Paul "TBBle" Hampson

As far as I know, this is the last open issue that prevents generally-found-on-the-Internet Dockerfiles from building correctly. The are two core difference from Linux containers at work here. First...

(Agree about the PR-issue thing. >_< I probably should have pushed out into an issue when I revived this last week, since I was already looking past the scope of...

Worth noting that on Windows, CMD is one of the few (only?) remaining tools in the Windows ecosystem that can't handle LF-only scripts. And it's still the default `SHELL` for...

Roughly, yeah. I was leaning towards normalised newlines for everything except the "write the file out to disk for the shell to execute" step, e.g., history annotations, debugging output, etc....

As far as Linux support is concerned, containerd containers a different snapshotter for Linux images on Windows, which AFAIK is storing the images in extfs4 image files, as seen in...

How does `FROM mcr.microsoft.com/windows/nanoserver:ltsc2022` build successfully on Windows Server 2019? That shouldn't work with either process isolation or HyperV isolation, AFAIK. The fact that the `USER` line fixes it suggests...

~~This one's not really area/windows, since this is Docker Desktop's WSL2 environment.~~ ~~And yeah, probably the same as #4643, although in this case it's the BuildKit embedded in buildx, and...

Try running the buildkit daemon with ``` docker run --rm --privileged -d --name buildkit --env "HTTP_PROXY=" --env "HTTPS_PROXY=" moby/buildkit ``` or if you already have the `HTTP_PROXY` and/or `HTTPS_PROXY` env-vars...

That error shows it's not getting or using the proxy settings, and is instead being transparently redirected to your corporate firewall (or possibly the local computer's firewall), which relies on...

My guess is that something's up with the networking environment of the docker daemon, that doesn't affect the docker-container driver when using host-networking. This could be a WSL2 issue of...