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

[Bug]: Segfault issue when installing libc-bin #755

Open
IanHoang opened this issue Feb 21, 2025 · 2 comments
Open

[Bug]: Segfault issue when installing libc-bin #755

IanHoang opened this issue Feb 21, 2025 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@IanHoang
Copy link
Collaborator

Describe the bug

ARM64 Docker Builds in PRs are failing due to the following error:

#11 83.18 Setting up libgd3:arm64 (2.3.0-2) ...
#11 83.18 Setting up libc-devtools (2.31-13+deb11u11) ...
#11 83.19 Processing triggers for libc-bin (2.31-13+deb11u5) ...
#11 83.24 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#11 83.59 Segmentation fault (core dumped)
#11 83.61 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#11 83.97 Segmentation fault (core dumped)
#11 83.97 dpkg: error processing package libc-bin (--configure):
#11 83.97  installed libc-bin package post-installation script subprocess returned error exit status 139
#11 83.99 Errors were encountered while processing:
#11 83.99  libc-bin
#11 84.16 E: Sub-process /usr/bin/dpkg returned an error code (1)
#11 ERROR: process "/bin/sh -c apt-get install -y curl git gcc pbzip2 pigz make jq" did not complete successfully: exit code: 100
------
 > [build-stage 3/6] RUN apt-get install -y curl git gcc pbzip2 pigz make jq:
#11 83.19 Processing triggers for libc-bin (2.31-13+deb11u5) ...
#11 83.24 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#11 83.59 Segmentation fault (core dumped)
#11 83.61 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#11 83.97 Segmentation fault (core dumped)
#11 83.97 dpkg: error processing package libc-bin (--configure):
#11 83.97  installed libc-bin package post-installation script subprocess returned error exit status 139
#11 83.99 Errors were encountered while processing:
#11 83.99  libc-bin
: Sub-process /usr/bin/dpkg returned an error code (1)
------
Dockerfile:11
--------------------
   9 |     
  10 |     RUN apt-get -y update
  11 | >>> RUN apt-get install -y curl git gcc pbzip2 pigz make jq
  12 |     RUN apt-get -y upgrade
  13 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get install -y curl git gcc pbzip2 pigz make jq" did not complete successfully: exit code: 100

This started to happen 2/17/2025 when @OVI3D0 opened up a new PR. Confirmed that it was not related to changes in his PR after I reran my Github actions (that previously succeeded) and saw that Docker ARM64 build workflow failed.

To reproduce

Run Docker Build Workflow Action on main branch or open a PR.

Expected behavior

No response

Screenshots

If applicable, add screenshots to help explain your problem.

Host / Environment

No response

Additional context

No response

Relevant log output

@IanHoang
Copy link
Collaborator Author

Similar issue on Docker Buildx docker/buildx#1170 (comment)

@IanHoang
Copy link
Collaborator Author

Github Actions for OSB is using 24.04. In line with how users are experiencing the issue with Ubuntu 24.04 + Qemu but not with Ubuntu 20.04

Runner Image
  Image: ubuntu-24.04
  Version: 20250209.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu24/2025020[9](https://github.com/IanHoang/opensearch-benchmark/actions/runs/13461950670/job/37619149746#step:1:10).1/images/ubuntu/Ubuntu2404-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20250209.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🏗 In progress
Development

No branches or pull requests

1 participant