setup-qemu-action: `tonistiigi/binfmt:latest` (qemu 9.2.0) segfault on ubuntu-24.04 / ubuntu-latest
Contributing guidelines
- I’ve read the contributing guidelines and wholeheartedly agree
I’ve found a bug, and:
- The documentation does not mention anything about my problem
- There are no open or closed issues that are related to my problem
Description
As mentioned in https://github.com/docker/setup-qemu-action/issues/188, the default image is unusable on ubuntu-24.04 since a kernel update a few weeks back.
As reported in that issue, moving to the qemu 8.1.5 image solved the issue for most users (since then, there has been a 9.2.0 / master image published).
It seems more & more unlikely that the latest image will be updated and more likely that setup-qemu-action should change the default image (possibly depending on the runner) to an image that works in most cases rather than what I imagine is almost none => hence this is a bug report setup-qemu-action can do something about without closing saying it’s an upstream issue.
Multiple reproducers/logs/… are already available in that issue so not added new ones here.
Expected behaviour
No random segmentation faults.
Actual behaviour
Random segmentation faults in all the repositories I know of when the action is used with the default image on ubuntu-24.04 (latest)
Repository URL
No response
Workflow run URL
No response
YAML workflow
N/C
Workflow logs
No response
BuildKit logs
Additional info
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 29
- Comments: 19 (2 by maintainers)
Commits related to this issue
- Merge pull request #1530 from bettio/run-qemu-on-ubuntu-22.04 Run qemu on Ubuntu 22.04 See also: - https://github.com/actions/runner-images/issues/11471 - https://github.com/docker/setup-qemu-action... — committed to atomvm/AtomVM by bettio 2 years ago
- Don't publish ARM Docker images for Server We're not currently running Server on ARM, so we don't really need this. This also allows to workaround QEMU segfaulting on ARM see https://github.com/docke... — committed to tensorlakeai/indexify by eabatalov 2 years ago
- Don't publish ARM Docker images for Server (#1220) We're not currently running Server on ARM, so we don't really need this. This also allows to workaround QEMU segfaulting on ARM see https://github... — committed to tensorlakeai/indexify by eabatalov 2 years ago
- Add workaround for issue with qemu on GHA runners https://github.com/docker/setup-qemu-action/issues/198 — committed to Graylog2/graylog-docker by bernd 2 years ago
- Pin QEMU binfmt image to work around a bug with ARM64 images This patch pins the binfmt image used by the setup-qemu-action to an older image to avoid a bug when building ARM64 images. See https://g... — committed to k8ssandra/management-api-for-apache-cassandra by emerkle826 2 years ago
- github: Pin a specific image for QEMU for Docker This fixes temporary breakage in building arm64 docker images on x86_64; see https://github.com/docker/setup-qemu-action/issues/198 and https://github... — committed to mstorsjo/llvm-mingw by mstorsjo 2 years ago
- [CI] Add container image build ci (#64) ### What this PR does / why we need it? Add container image build ci: - Enable branch, tag docker image publish - branch image: `vllm-ascend:main`, `vllm-a... — committed to vllm-project/vllm-ascend by Yikun 2 years ago
- Hotfix: Pin qemu-action to qemu-v7.0.0-28 Pinning qemu-action to known working version of qemu due to https://github.com/docker/setup-qemu-action/issues/198 — committed to Ptero-Eggs/yolks by danny6167 2 years ago
- chore: pinning qemu version, see https://github.com/docker/setup-qemu-action/issues/198 — committed to ekino/docker-buildbox by axelpavageauekino 2 years ago
- fix: temporrary fix for https://github.com/docker/setup-qemu-action/issues/198 Signed-off-by: deadprogram <ron@hybridgroup.com> — committed to hybridgroup/gocv by deadprogram 2 years ago
- [v0.7.1][CI] Add container image build ci (#65) ### What this PR does / why we need it? Backport https://github.com/vllm-project/vllm-ascend/pull/64 to v0.7.1-dev branch Add container image build c... — committed to vllm-project/vllm-ascend by Yikun 2 years ago
- fix: different temporary fix for https://github.com/docker/setup-qemu-action/issues/198 Signed-off-by: deadprogram <ron@hybridgroup.com> — committed to hybridgroup/gocv by deadprogram 2 years ago
- fix: yet different temporary fix for https://github.com/docker/setup-qemu-action/issues/198 Signed-off-by: deadprogram <ron@hybridgroup.com> — committed to hybridgroup/gocv by deadprogram 2 years ago
- fix: with both temporary fixes for https://github.com/docker/setup-qemu-action/issues/198 Signed-off-by: deadprogram <ron@hybridgroup.com> — committed to hybridgroup/gocv by deadprogram 2 years ago
- fix: with older qemu image for https://github.com/docker/setup-qemu-action/issues/198 Signed-off-by: deadprogram <ron@hybridgroup.com> — committed to hybridgroup/gocv by deadprogram 2 years ago
- chore: pinning qemu version, see https://github.com/docker/setup-qemu-action/issues/198 — committed to ekino/docker-buildbox by axelpavageauekino 2 years ago
- Pin QEMU binfmt image to work around a bug with ARM64 images This patch pins the binfmt image used by the setup-qemu-action to an older image to avoid a bug when building ARM64 images. See https://g... — committed to k8ssandra/management-api-for-apache-cassandra by emerkle826 2 years ago
- Fix CI segfault See https://github.com/docker/setup-qemu-action/issues/198 --- Pull Request resolved: https://github.com/doublecloud/transfer/pull/218 commit_hash:c16917fdbf4cafa8c0eaf16e04cdf656f2... — committed to transferia/transferia by kamushadenes 2 years ago
- chore: pinning qemu version, see https://github.com/docker/setup-qemu-action/issues/198 — committed to ekino/docker-buildbox by axelpavageauekino 2 years ago
- fix: temporary fix for https://github.com/docker/setup-qemu-action/issues/198 Signed-off-by: deadprogram <ron@hybridgroup.com> — committed to hybridgroup/gocv by deadprogram 2 years ago
We are mysteriously encountering this issue on ARM64 self-hosted GitHub Actions (
ghcr.io/actions/actions-runner:2.322.0) based runners, beginning sometime over the past 72 hours, targeting AMD64. None of the workarounds have worked for us. Anyone else in the same boat?Part of the challenge is that
setup-qemu-actionis pointing to:latesttag by default. I’d suggest switching to a more specific tag for every release. One, that was used to test this specific release. Immutable Github actions will fix this problem long term, but relying on:latestis wrong and must be fixed.Same issue
I mentioned it in another issue (here) but I found another workaround as well. If you set up your
Dockerfileas a multi-stage build withmultiarch/qemu-user-staticas a base and inject the QEMU binaries into your target image, no segfaults will generate. Here’s an example:This was tested on Windows 10 Pro x64 host machine while building docker images to be used on Raspberry Pi 3s (
linux/arm/v7) and 4s (linux/arm64/v8). To be clear, only thelinux/arm64/v8builds were failing.I’d like to know why this works, as this seems too simple for my liking but I’m glad this is a decent workaround for now.