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

ldconfig question #36

Closed
mrhjx2 opened this issue Dec 19, 2019 · 4 comments
Closed

ldconfig question #36

mrhjx2 opened this issue Dec 19, 2019 · 4 comments

Comments

@mrhjx2
Copy link

mrhjx2 commented Dec 19, 2019

when use Dockerfile build and question is

Executing glibc-bin-2.30-r0.trigger
/usr/glibc-compat/sbin/ldconfig: /usr/glibc-compat/lib/ld-linux-x86-64.so.2 is not a symbolic link

OK: 46 MiB in 21 packages
failed to set locale!
[warning] No definition for LC_PAPER category found
failed to set locale!
[warning] No definition for LC_NAME category found
failed to set locale!
[warning] No definition for LC_ADDRESS category found
failed to set locale!
[warning] No definition for LC_TELEPHONE category found
failed to set locale!
[warning] No definition for LC_MEASUREMENT category found
failed to set locale!
[warning] No definition for LC_IDENTIFICATION category found
@frol
Copy link
Member

frol commented Dec 19, 2019

What is your question?

@tekumara
Copy link

I also get the ldconfig error message when running make:

$ docker run --rm -it frolvlad/alpine-glibc         

/ # apk add --no-cache curl
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz
(1/4) Installing ca-certificates (20191127-r4)
(2/4) Installing nghttp2-libs (1.41.0-r0)
(3/4) Installing libcurl (7.69.1-r3)
(4/4) Installing curl (7.69.1-r3)
Executing busybox-1.31.1-r19.trigger
Executing ca-certificates-20191127-r4.trigger
Executing glibc-bin-2.32-r0.trigger
/usr/glibc-compat/sbin/ldconfig: /usr/glibc-compat/lib/ld-linux-x86-64.so.2 is not a symbolic link

OK: 19 MiB in 22 packages

Is the ld-linux-x86-64.so.2 is not a symbolic link message an issue, and is it possible to resolve it?

@tekumara
Copy link

Looks like this is a warning that can be ignored, see envoyproxy/envoy#9078 (comment)

@frol
Copy link
Member

frol commented Jan 20, 2021

It seems that this question is stale, so I close it.

@frol frol closed this as completed Jan 20, 2021
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

3 participants