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

symbolic-link issue on docker-compose in MAC OSX #9078

Closed
c0debreaker opened this issue Nov 20, 2019 · 5 comments
Closed

symbolic-link issue on docker-compose in MAC OSX #9078

c0debreaker opened this issue Nov 20, 2019 · 5 comments
Labels
area/build stale stalebot believes this issue/PR has not been touched recently

Comments

@c0debreaker
Copy link

I'm on Mac OSX High Sierra.

I ran docker-compose up --build -d in examples/front-proxy. It completed successfully. However, I saw an error. You can see the error the last line below.

Step 2/8 : RUN apk update && apk add python3 bash curl
 ---> Running in c6776618cf7e
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz
v3.10.3-46-gd7d7d0f8fd [http://dl-cdn.alpinelinux.org/alpine/v3.10/main]
v3.10.3-43-gcc200417b2 [http://dl-cdn.alpinelinux.org/alpine/v3.10/community]
OK: 10343 distinct packages available
(1/16) Installing ncurses-terminfo-base (6.1_p20190518-r0)
(2/16) Installing ncurses-terminfo (6.1_p20190518-r0)
(3/16) Installing ncurses-libs (6.1_p20190518-r0)
(4/16) Installing readline (8.0.0-r0)
(5/16) Installing bash (5.0.0-r0)
Executing bash-5.0.0-r0.post-install
(6/16) Installing ca-certificates (20190108-r0)
(7/16) Installing nghttp2-libs (1.39.2-r0)
(8/16) Installing libcurl (7.66.0-r0)
(9/16) Installing curl (7.66.0-r0)
(10/16) Installing libbz2 (1.0.6-r7)
(11/16) Installing expat (2.2.8-r0)
(12/16) Installing libffi (3.2.1-r6)
(13/16) Installing gdbm (1.13-r1)
(14/16) Installing xz-libs (5.2.4-r0)
(15/16) Installing sqlite-libs (3.28.0-r1)
(16/16) Installing python3 (3.7.5-r1)
Executing busybox-1.30.1-r2.trigger
Executing ca-certificates-20190108-r0.trigger
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
@junr03
Copy link
Member

junr03 commented Nov 20, 2019

@lizan could you take a look at this?

@stale
Copy link

stale bot commented Dec 20, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Dec 20, 2019
@c0debreaker
Copy link
Author

Does this mean it has been solved?

@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Dec 20, 2019
@stale
Copy link

stale bot commented Jan 19, 2020

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Jan 19, 2020
@zuercher
Copy link
Member

This is a warning printed by the package manager in the underlying docker image. ldconfig anticipates multiple glibc versions with a symbolic link from the common name (ld-linux-x86-64.so.2) to the latest installed version (which allows apps that require a specific version to load it directly). In this image, there's exactly one version and no symbolic link. I don't believe this is a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

3 participants