-
-
Notifications
You must be signed in to change notification settings - Fork 283
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
2.35-r0: Missing symbols __*_chk
#176
Comments
Can confirm this, we had to roll back to 2.34-r0 as well as otherwise our pipeline breaks |
Our developers have just noticed this as well. Thanks @TechRabb1t rolling back worked. |
Happened the same to me and roll back to 2.34-r0 as previous comments mentioned. Thanks! |
You're referencing symbols which shouldn't be available in the C library at runtime. From the look of it they're in the |
I believe these symbols are all normally there and part of glibc, e.g
I agree with @prantlf that this seems to be essentially the same as the other issues. This seems to happen when
Can replicate with the below where both docker build . --platform linux/amd64 --progress=plain FROM alpine:3.17
RUN apk add --no-cache tzdata --virtual .build-deps curl binutils zstd && \
GLIBC_VER="2.35-r1" && \
ALPINE_GLIBC_REPO="https://github.com/sgerrand/alpine-pkg-glibc/releases/download" && \
ZLIB_URL="https://archive.archlinux.org/packages/z/zlib/zlib-1%3A1.2.13-2-x86_64.pkg.tar.zst" && \
ZLIB_SHA256=c4f394724b20b84d7304b23bbb58442b6ef53e5cbac89eb51e39d7f0a46abafd && \
curl -LfsS https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub -o /etc/apk/keys/sgerrand.rsa.pub && \
SGERRAND_RSA_SHA256="823b54589c93b02497f1ba4dc622eaef9c813e6b0f0ebbb2f771e32adf9f4ef2" && \
echo "${SGERRAND_RSA_SHA256} */etc/apk/keys/sgerrand.rsa.pub" | sha256sum -c - && \
curl -LfsS ${ALPINE_GLIBC_REPO}/${GLIBC_VER}/glibc-${GLIBC_VER}.apk > /tmp/glibc-${GLIBC_VER}.apk && \
apk add --no-cache --force-overwrite /tmp/glibc-${GLIBC_VER}.apk && \
# mkdir -p /lib64 && ln -sf /usr/glibc-compat/lib/ld-linux-x86-64.so.2 /lib64/ld-linux-x86-64.so.2 && \
curl -LfsS ${ZLIB_URL} -o /tmp/libz.tar.zst && \
echo "${ZLIB_SHA256} */tmp/libz.tar.zst" | sha256sum -c - && \
curl -LfsS ${ALPINE_GLIBC_REPO}/${GLIBC_VER}/glibc-bin-${GLIBC_VER}.apk > /tmp/glibc-bin-${GLIBC_VER}.apk && \
apk add --no-cache --force-overwrite /tmp/glibc-bin-${GLIBC_VER}.apk && \
mkdir /tmp/libz && \
zstd -d /tmp/libz.tar.zst --output-dir-flat /tmp && \
tar -xf /tmp/libz.tar -C /tmp/libz && \
curl --silent --fail --location https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip --output /tmp/awscliv2.zip && \
unzip -q /tmp/awscliv2.zip && \
ls -al /lib64 && /aws/dist/aws --version 2.34.r0 (OK)
2.35-r1 (Not OK)
This seems to be happening with
ddfe092#diff-9d02a9f5b32ef57f03edeea2673bf874facd3f51789e70184f4488e4fe89541cL17-R18 These issues seem to have been partially addressed in #180 which got stuck (and still not sure why it makes sense to install Hope this helps clarify. |
still does not work
|
…1 related build issues @see: sgerrand/alpine-pkg-glibc#176
…1 related build issues @see: sgerrand/alpine-pkg-glibc#176
…1 related build issues @see: sgerrand/alpine-pkg-glibc#176
…1 related build issues @see: sgerrand/alpine-pkg-glibc#176
…1 related build issues @see: sgerrand/alpine-pkg-glibc#176
When updating a Docker container to use glibc
2.35-r0
(previously used2.34-r0
) I am seeing the following errors during the container build:These errors weren't there with
2.34-r0
so it is likely something that has changed in2.35-r0
?The text was updated successfully, but these errors were encountered: