-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-stage buildx build corrupts character special files #1027
Comments
JRaspass
added a commit
to code-golf/code-golf
that referenced
this issue
Mar 27, 2022
This moves the creation of /dev to runtime in run-lang.c, this is to workaround github.com/docker/buildx/issues/1027. This unblocks us moving to buildx/BuildKit in the near future. It's not ideal but the cost to doing it at runtime is minimal. As part of this every lang needed a rebuild some everything is now on the latest Alpine and V naturally needed a bump to build.
I am running buildx v0.12.0 and buildkit v0.12.5 and the problem seems to be solved now! |
This seems to be working fine now. |
JRaspass
added a commit
to code-golf/code-golf
that referenced
this issue
Aug 10, 2024
Now that docker/buildx#1027 is fixed we can populate /dev at build-time rather than runtime. This also seems to fix the Zig issue of needing a chown.
Yewzir
pushed a commit
to Yewzir/code-golf
that referenced
this issue
Dec 14, 2024
Now that docker/buildx#1027 is fixed we can populate /dev at build-time rather than runtime. This also seems to fix the Zig issue of needing a chown.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Single-stage (works)
docker build
docker buildx
Multi-stage (builx doesn't work)
docker build
docker buildx
(note the lack of c in/my-urandom
)I noticed this when switching an application to buildx that specifically doesn't mount the hosts /dev and just populates what it needs (like /dev/urandom) and those reads were blocking indefinitely since buildx had made a zero byte regular file instead.
Now it may be that this isn't a bug and that character special files aren't supported but I would argue it's at least a little surprising when both legacy
docker build
anddocker buildx
with single-stage build both worked.The text was updated successfully, but these errors were encountered: