ci: add multi-arch ARM64 support using native runners#34
Open
soile1991 wants to merge 1 commit into
Open
Conversation
soile1991
force-pushed
the
feature/arm-docker-support
branch
from
75fcb07 to
8dd62a0
Compare
mikeknight85
added a commit
to mikeknight85/PriceStalker
that referenced
this pull request
Apr 21, 2026
Version bump to accompany the cherry-picked multi-arch CI change from upstream PR clucraft#34 (previous commit). Images published from v1.2.3 onward are manifest lists covering both linux/amd64 and linux/arm64, unlocking native runs on Apple Silicon, Raspberry Pi, AWS Graviton, etc. No change for existing x86 users — Docker picks the right variant automatically. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replace the single-job amd64-only workflow with a native runner matrix strategy to produce proper multi-arch Docker images without QEMU. Why QEMU doesn't work: - Node.js V8 JIT generates instructions QEMU user-mode emulation mis-handles, causing SIGILL crashes during npm install on arm64. How it works now: - linux/amd64 builds on ubuntu-latest (native) - linux/arm64 builds on ubuntu-24.04-arm (native GitHub ARM runner) - Each job pushes its image by digest to GHCR - A merge job combines both digests into a single multi-arch manifest list via docker buildx imagetools create Also removes the dorny/paths-filter changes job — the on.push.paths trigger already gates the workflow to relevant file changes, so the extra conditional layer is unnecessary.
soile1991
force-pushed
the
feature/arm-docker-support
branch
from
6107b0d to
fc1f78f
Compare
soile1991
changed the title
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.
Problem
The CI workflow only built
linux/amd64images. Two attempts were made with QEMU emulation but both failed:Illegal instructioncrash duringnpm installon the emulated arm64 layer.Solution
Use GitHub's native
ubuntu-24.04-armrunner for the ARM64 build — no emulation at all.How it works
Each image is built in a matrix across two native runners:
linux/amd64ubuntu-latestlinux/arm64ubuntu-24.04-armEach job pushes its image layer by digest to GHCR. A final
mergejob combines both digests into a single multi-arch manifest list withdocker buildx imagetools create, producing a standard manifest that transparently serves the right layer on any platform.Other changes
dorny/paths-filterchanges job — theon.push.pathstrigger already gates the workflow to relevant changes, making the extra conditional layer unnecessary.docker/build-push-actionfrom v5 → v6.