Open dev-fredericfox opened 5 months ago
Is there any chance it's https://github.com/moby/buildkit/issues/3965 (see also https://github.com/moby/buildkit/issues/3898).
That's the only immediately-findable BuildKit issues I could find for that error message, and I guess it's possible that the ShaderCompileWorker
build step created a UNIX socket, causing the WORKDIR
step to fail.
There's a very short repro case at the top of https://github.com/moby/buildkit/issues/3965 which should be able to verify that, and then per https://github.com/moby/buildkit/issues/3898 it might be as simple as changing the Docker config to use overlay2
, although that should be the default already...
Either way, it might help for further investigation to log the output of docker info
.
Output of the
ue4-docker info
command:Additional details:
After the annoying MacM3 issues, I have found an old intel machine. It's running a Debian live distro on a 1TB ssd. Now I am stuck on step 12/20. Thoughts?
I run the repair command and rebuild the container, but yet again got the same message with some other ID's
I also deleted docker and ue4-docker and reinstalled it.