Skip to content

Commit

Permalink
Hotfix: Lock quemu to a version that does not segfault (#55)
Browse files Browse the repository at this point in the history
The build pipeline started failing recently. It was crashing with this error:
```
45.34 Preparing to unpack .../libc-bin_2.35-0ubuntu3.9_arm64.deb ...
45.35 Unpacking libc-bin (2.35-0ubuntu3.9) over (2.35-0ubuntu3.8) ...
45.60 Setting up libc-bin (2.35-0ubuntu3.9) ...
45.73 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
46.18 Segmentation fault (core dumped)
46.24 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
46.60 Segmentation fault (core dumped)
Sub-process /usr/bin/dpkg returned an error code (1)
```

I managed to dig a working version from the history of successful builds. If I managed to check correctlu that was using quemu 7.0.0 and the default version used (":latest") was using 9.2.0.

Doesn't seem like there's any tags any longer for the 7.0.0 images,
  • Loading branch information
joakimnordling authored Feb 12, 2025
1 parent 57ec76c commit 1d8277b
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion .github/workflows/build-and-upload.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,13 @@ jobs:
run: regctl version

- name: Set up QEMU
uses: docker/setup-qemu-action@v2
uses: docker/setup-qemu-action@v3
with:
# For now hardcoding the image to the latest version found in a successful run of the action, it seems like
# it is using quemu v7.0.0. The "tonistiigi/binfmt:latest" with qemu-v9.2.0 runs into this error:
# Setting up libc-bin (2.35-0ubuntu3.9) ...
# qemu: uncaught target signal 11 (Segmentation fault) - core dumped
image: "tonistiigi/binfmt@sha256:66e11bea77a5ea9d6f0fe79b57cd2b189b5d15b93a2bdb925be22949232e4e55"

- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
Expand Down

0 comments on commit 1d8277b

Please sign in to comment.