-
Notifications
You must be signed in to change notification settings - Fork 384
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
Error when COPY --from=builder /lib/ld-musl-x86_64.so.1 /lib/ld-musl-x86_64.so.1: #300
Comments
I can't seem to reproduce this error:
```
---> c215d77c7ff4
Step 10/15 : FROM scratch
--->
Step 11/15 : COPY --from=builder /builddir/sslscan /sslscan
---> 49d45d65664c
Step 12/15 : COPY --from=builder /lib/libz.so.1 /lib/libz.so.1
---> e0c99f39eba2
Step 13/15 : COPY --from=builder /lib/ld-musl-x86_64.so.1 /lib/ld-musl-
x86_64.so.1
---> 6b63a33358a0
Step 14/15 : USER 65535:65535
---> Running in 1843bec11fce
Removing intermediate container 1843bec11fce
---> 7b696eb989b1
Step 15/15 : ENTRYPOINT ["/sslscan"]
---> Running in fb3ef2ddfd7f
Removing intermediate container fb3ef2ddfd7f
---> cded6018ffc1
Successfully built cded6018ffc1
```
This is using the `master` branch of sslscan, along with Docker
v24.0.5. What code branch and Docker version are you using?
|
I am on master branch:
I am working on Mac OS M1 Max, Sonoma 14.1.2. I did run again and got the same:
|
Does |
It just occurred to me: alpine:latest is likely the ARM build on
MacOSX/M1, whereas its x86_64 on our machines. Hence, there is no ld-
musl-x86_64.so.1 on ARM; its probably called ld-musl-arm.so.1 or
something.
@derekmizak: on line 26 of the Dockerfile, could you change it to read
"COPY --from=builder /lib/ld-musl-*.so.1 /lib/" and try again?
|
@jtesta - it worked. Thank you. All is fine - can be closed.
|
@derekmizak that should be merged into master now. @jtesta, I suspected that it would be something like that when I saw the error - but TBH I've never really looked at the ARM docker images. |
It is fixed - thank you. |
There is an error when building docker:
The text was updated successfully, but these errors were encountered: