Skip to content

ci: pin newer QEMU to fix hung arm64 image build #6

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.

Sign up for GitHub

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

Merged
StrandedTurtle merged 1 commit into from
Jun 25, 2026
Merged

ci: pin newer QEMU to fix hung arm64 image build #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@ on:
branches: [main]
tags: ["v*"]

# Only one publish run per ref at a time; a newer push cancels an in-flight
# build for the same ref instead of letting it hang/queue behind it.
concurrency:
group: publish-${{ github.ref }}
cancel-in-progress: true

jobs:
publish:
name: Build and push to GHCR
Expand Down Expand Up @@ -35,7 +41,14 @@ jobs:
type=raw,value=edge,enable=${{ github.ref == 'refs/heads/main' }}
type=raw,value=latest,enable=${{ startsWith(github.ref, 'refs/tags/v') }}

# Pin a recent QEMU build. The default binfmt image lagged the toolchain
# in node:22-alpine (gcc 15 / musl 1.2.6), and emulating those newer
# arm64 binaries crashed with "uncaught target signal 4 (Illegal
# instruction)", which core-dumped and left the build hung. A current
# QEMU emulates the new userspace correctly.
- uses: docker/setup-qemu-action@v3
with:
image: tonistiigi/binfmt:qemu-v10.2.3
- uses: docker/setup-buildx-action@v3

- name: Log in to GHCR
Expand Down
Loading