ci: pin QEMU binfmt for the arm64 cross-build (pre-empt the blox-ai segfault)#77
Merged
Conversation
ARCH_SUPPORT is linux/arm64-only, so every image is cross-built under QEMU on
the amd64 runner. The workflow had no setup-qemu-action and relied on the
runner's default binfmt, which can segfault ("qemu: uncaught target signal 11")
emulating arm64 dpkg/libc-bin in the fula-gateway apt-get layer -- the same
failure blox-ai hit on 2026-06-18 (fixed there by the same pin, validated green).
Add setup-qemu-action with a pinned tonistiigi/binfmt to every build job so the
arm64 cross-build is reproducible. Defensive: fula-ota's last release build was
green 2026-06-01 on the runner default, but the runner image evolves and the
apt-get pattern is identical to the one that regressed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
ARCH_SUPPORT="linux/arm64"— every image is cross-built under QEMU emulation on the amd64 runner. This workflow had nosetup-qemu-actionand relied on the runner's default binfmt.On 2026-06-18 the sibling repo blox-ai (which does use
setup-qemu-action) failed its arm64 build withqemu: uncaught target signal 11 (Segmentation fault)whiledpkgranlibc-bin's post-install duringapt-get install— a QEMU emulation regression (the same Dockerfile was green weeks earlier).fula-gateway's Dockerfile does the same Debianapt-get install, so fula-ota's release build is at risk of the identical crash.What
Add
docker/setup-qemu-action@v3pinned totonistiigi/binfmt:latestahead of buildx in every job. This pin is validated — it took blox-ai's arm64 build from red to green (thelibc-bintrigger processed cleanly under it).Honest caveat
fula-ota's last release build was green on 2026-06-01 using the runner's default QEMU — a different QEMU source from blox-ai's
setup-qemu-actionbinfmt. So this is defensive: fula-ota might not have hit the bug, but theapt-getpattern is identical and the pin is low-risk (a known-good QEMU + standard practice for arm64 cross-builds). Recommend merging before the next release build so a rebuild doesn't risk a second red build.:latestis a moving tag; pin a specificqemu-vX.Y.Zif reproducibility is preferred.🤖 Generated with Claude Code