-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 alpine 19 #8423
Comments
Hello, |
Hi, I found the same segmentation fault problem using Fedora Linux 35 x86-64. |
Hi, thanks for reaching out and for your patience. If it produces meaningful logging before the error, could you provide debug logs of a command resulting in a segmentation fault? You can get debug logs by adding |
Thanks @RyanFitzSimmonsAK! I ran |
I'm getting seg fault on install, and if I try and run "install --debug", I get "Got an unexpected argument: --debug" Edit: ^^^ This is install from the download (https://awscli.amazonaws.com/awscli-exe-linux-x86_64-${AWS_CLI_VERSION}.zip). Switching to using the apk in the registry works. |
bump this, I got the error also and did some investigating on Dec 7, 3.19 alpine came out terraform uses the latest alpine in its docker hub image here: terraform/Dockerfile at 53c34ff49cfbc1f70d7cdd3dca8040551c53737a · hashicorp/terraform (github.com) terraform 1.66 came out on dec 13 and built on alpine 3.19 Tags · hashicorp/terraform (github.com) I got the error using the above docker hub image in circle ci which is based on alpine 3.19 If I change to terraform 1.65 image (alpine 3.18) all of the above works fine. I tested with aws-cli 2.15.15 and 2.15.3, both are broken, I did not go furth back than that. |
This works in 3.19: |
Installing package is fine, running the cli after install is what throws a segmentation fault for me. |
Running into same seg fault core dump issues with alpine 3.19. |
Could be an issue with the linker
|
if you are on circleci, using the aws cli orb and can go to the latest aws cli 2.13.25 , then you can upgrade your orb: https://github.com/CircleCI-Public/aws-cli-orb/releases/tag/v4.1.3 @otremblay and @brentmmarks helped fix the orb that had a workaround before for alpine: CircleCI-Public/aws-cli-orb@c5a792e of specific interest: upgrade of orb: also this old issue shows that same method of install here: apk add --no-cache aws-cli |
Please refer to the documentation to Build and install the AWS CLI from source for this use case. As noted there, Alpine Linux uses musl, but the current installers require FROM python:3.11-alpine3.19 AS builder
ENV AWSCLI_VERSION=2.17.21
RUN apk add --no-cache \
curl \
make \
cmake \
gcc \
g++ \
libc-dev \
libffi-dev \
openssl-dev \
&& curl https://awscli.amazonaws.com/awscli-${AWSCLI_VERSION}.tar.gz | tar -xz \
&& cd awscli-${AWSCLI_VERSION} \
&& ./configure --prefix=/opt/aws-cli/ --with-download-deps \
&& make \
&& make install
FROM python:3.11-alpine3.19
RUN apk --no-cache add groff
COPY --from=builder /opt/aws-cli/ /opt/aws-cli/
ENTRYPOINT ["/opt/aws-cli/bin/aws"] |
Describe the bug
Any command run under alpine 3.19 results in segmentation error.
Alpine linux 3.19 has been included in docker images just recently, definietly related.
Expected Behavior
Works fine under the latest alpine image.
Current Behavior
Crashes with segmentation fault
Reproduction Steps
It can be reproduced in a docker image.
Chaging the source image:
FROM docker:24.0.7-dind-alpine3.18
and everything works fine.Possible Solution
No response
Additional Information/Context
No response
CLI version used
aws-cli/2.13.29 Python/3.11.6 Linux/6.2.0-39-generic exe/x86_64.alpine.3 prompt/off
Environment details (OS name and version, etc.)
Alpine linux 3.19 (official docker:dind image)
The text was updated successfully, but these errors were encountered: