-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Missing libssl.so.x.x
symlink in final docker image
#1394
Comments
Thanks. From the options you presented, we'd ideally use the same image. Maybe we could change it to rust:slim-buster, which would ensure that the image stays small? |
The current lychee docker image (available via I think the best solution is to, instead, ensure the two base images use the same Debian version. I tested the I'd suggest using |
Yes, I can. The executable isn't stripped in Dockerfile as it is in the GitHub Releases here. I have realised that the |
As far as I can see, this can be closed because of the excellent work by @MattTimms. (The libssl issues should be resolved now; please reopen in case that's incorrect.) |
This only affects newly built images;
docker pull lycheeverse/lychee
as per the README fetches a working image ("Created": "2024-03-22T23:29:28.775271855Z"
).Due to the floating versions of the base images used in the
Dockerfile
, i.e.rust:latest
&debian:bullseye-slim
, there is a issue between thelibssl-dev
version of thebuilder
stage & that of the final base image. This causes the following error when running a freshly built container:lychee: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
As of time of writing, building the
Dockerfile
fetches:The contents of
/usr/lib/x86_64-linux-gnu/
for each of these images is:libssl.so
,libssl.so.3
forrust:latest
, &libssl.so.1.1
fordebian:bullseye-slim
. Hence, the lychee from builder is expectedlibssl.so.3
where the final image contains onlylibssl.so.1.1
.Solutions could be to:
Dockerfile
to create a symlink for the expectedlibssl.so.x.x
file, assuming its compatible across base-images.FROM rust@sha256:...
The text was updated successfully, but these errors were encountered: