Skip to content
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.

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

Segmentation Fault on latest x86_64 Ubuntu 24.04 image (I KNOW) #52

Closed
lattwood opened this issue Feb 12, 2025 · 7 comments
Closed

Segmentation Fault on latest x86_64 Ubuntu 24.04 image (I KNOW) #52

lattwood opened this issue Feb 12, 2025 · 7 comments

Comments

@lattwood
Copy link

When using QEMU to emulate ARM on an x86_64 system, a segmentation fault occurs. Although it isn’t immediately clear why this issue is being categorized as a partner-runner-images problem, I am filing it here based on community guidance and previous reports.

Multiple people have tried opened issues on actions/runner-images, as that is where the runner image in use comes from-

but the issues were closed and they were told to come here.

While this approach may seem counterintuitive (much like troubleshooting a recurring connection issue by restarting your router) it is intended to ensure that the problem receives the correct level of attention. I hope that by documenting this behaviour in accordance with the recommendations from the actions/runner-images contributors, the underlying cause can be thoroughly investigated.

@alexanderkiel
Copy link

This breaks my build. Also doesn't work in ubuntu-22.04 version 20250209.1.0. Did last work in ubuntu-24.04 version 20250202.1.0. Current seqfault occurs during apt-get upgrade inside eclipse-temurin:21.0.6_7-jre-jammy.

#10 44.04 Preparing to unpack .../libc-bin_2.35-0ubuntu3.9_arm64.deb ...
#10 44.05 Unpacking libc-bin (2.35-0ubuntu3.9) over (2.35-0ubuntu3.8) ...
#10 44.30 Setting up libc-bin (2.35-0ubuntu3.9) ...
#10 44.43 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#10 44.78 Segmentation fault (core dumped)
#10 44.84 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#10 45.20 Segmentation fault (core dumped)
#10 45.21 dpkg: error processing package libc-bin (--configure):
#10 45.21  installed libc-bin package post-installation script subprocess returned error exit status 139
#10 45.22 Errors were encountered while processing:
#10 45.22  libc-bin
#10 45.35 E: Sub-process /usr/bin/dpkg returned an error code (1)

@alexanderkiel
Copy link

Updating to eclipse-temurin:21.0.6_7-jre-noble, which itself is an ubuntu-24.04 solved the issue for me. With that base image, I can run the apt-get upgrade shown above. All that in the runner-image ubuntu-24.04 version 20250209.1.0.

@krzyzakp
Copy link

Have same issue, using the 22.04 - jammy.

@henkhofs
Copy link

For me the issue was fixed by adding a specific qemu version to the setup-qemu action in my docker build and push composite action:

   - name: Set up QEMU
      uses: docker/setup-qemu-action@v3
      with:
        image: tonistiigi/binfmt:qemu-v7.0.0-28

@jasonrandrews
Copy link
Collaborator

Closing this as it is not about the Arm partner runner images. Good to know that qemu can emulate Arm better on x86 with the version info.

@dafcioo
Copy link

dafcioo commented Feb 24, 2025

Since all related issue reports have been closed, I would like to ask for clarification on the actual fix. Could you provide a straightforward explanation here? Specifically, which x86 runner image version is expected to work correctly for Build-Target Linux/ARM64?

No longer relevant since actions/runner-images#11662 has been opened.

@krzyzakp
Copy link

@henkhofs Tried also that version as saw it should fix it. But it doesn't fix it for me. Even with such version getting error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants