-
Notifications
You must be signed in to change notification settings - Fork 69
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
Docker build fails when apt is installing libc-bin #199
Labels
Comments
Thanks for the response. Sorry, I did look through issues, but didn't notice that there was one that was related. Unfortunately, this is a multi-stage build involving multiple private repos/images. I'll see if I can find a minimal repro and share, though. |
Same issue for arm64 |
BalduinLandolt
pushed a commit
to dasch-swiss/dsp-ingest
that referenced
this issue
Feb 18, 2025
ARM builds have recently stopped working due to docker/setup-qemu-action#198 Our errors ``` [error] 44.35 Setting up libc-bin (2.35-0ubuntu3.9) ... [error] 44.48 qemu: uncaught target signal 11 (Segmentation fault) - core dumped [error] 44.84 Segmentation fault (core dumped) ``` match with what's described in docker/setup-qemu-action#199 The temporary workaround seems to be pinning qemu to an older version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Contributing guidelines
I've found a bug, and:
Description
Our CI recently starting failing with a core dump when apt is instalilng libc-bin. Specifying an older version of the binfmt image works around the issue.
Expected behaviour
No errors and build completes properly.
Actual behaviour
I see the following error:
I saw that a new image was recently pushed, so went back to the previous version, which doesn't have this issue:
I'm not sure if it matters for this, but we have been on v2 of this action. I did try the latest and it didn't make a difference.
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
Additional info
No response
The text was updated successfully, but these errors were encountered: