Paul "TBBle" Hampson

Huh, weird, I didn't see the TTY issue in my original testing. I wonder if something changed since then, or if my test setup was so trivial it didn't trigger...

Rebased to main since I was going to fix the typo that turned out to not be a typo, so instead we get a trivial rebase.

Oops, looks like we never opened an issue for number 2 in https://github.com/containerd/nerdctl/pull/2587#issuecomment-1970588592.

Just came across this issue from #420, which turns out to be GCE specific from August 2023, and hence is probably what @sam-sla was seeing and maybe @Eishi2012, but that...

I haven't had a chance to play with IPv6 in Windows containers, but a quick look at that route table shows no default gateway for IPv6, suggesting that IPv6 is...

I can reproduce this, but only if I build with ``` docker build . --output . ``` If I have the Dockerfile somewhere else, I can run ``` docker build...

Rereading this ticket, is it only failing at ’RUN’? If so, that just seems like the nanoserver image's root ACLs or default user have changed in the LTSC 2022 release......

You are specifying process isolation, right? The immediate jump-out for client SKU-specific behaviour is the default being HyperV isolation in Docker, although on reflection I don't think BuildKit or containerd...

If I'm reading the output correctly, in both cases ContainerUser belongs to the same groups (both show `NT AUTHORITY\Authenticated Users`), the difference is actually that the CACLs list on Windows...

This seems like an unexpected gap in the isolation model, it suggests that even though we're mounting our filesystem over in another silo (if I remember correctly) it's still inheriting...