Interesting! I'm kind of perplexed because the image has worked before (and now it doesn't). When was this dependency added? I don't see any install of libssl in the azure pipelines, so is the feature not tested?

It's kind of perplexing that the same base and install commands leads to different versions - here is nu-base:

root@fcbeacc43e48:/code# ldconfig --verbose | grep ssl      
ldconfig: Can't stat /usr/local/lib/x86_64-linux-gnu: No such file or directory
ldconfig: Path `/lib/x86_64-linux-gnu' given more than once
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
ldconfig: /lib/x86_64-linux-gnu/ld-2.28.so is the dynamic linker, ignoring

	libssl.so.1.1 -> libssl.so.1.1

(correct) and here is nushell/nu:

root@31308c1e8884:/# ldconfig --verbose | grep ssl      
/sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
/sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than once
/sbin/ldconfig.real: /lib/x86_64-linux-gnu/ld-2.23.so is the dynamic linker, ignoring

	libssl.so.1.0.0 -> libssl.so.1.0.0
root@31308c1e8884:/#

Does the actual build of nu somewhere specify to install a different version? I modified the recipe down to be exactly the same (for the apt-get installs and base image):

ARG FROMTAG=latest
FROM quay.io/nushell/nu-base:${FROMTAG} as base
FROM ubuntu:16.04
COPY --from=base /usr/local/bin/nu /usr/local/bin/nu
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update && apt-get install -y libssl-dev \
    libxcb-composite0-dev \
    pkg-config \
    curl
ENTRYPOINT ["nu"]
CMD ["-l", "info"]

And it still seems to install a different version of libssl, so I'm thinking that cargo is somehow involved. Is it a fix to try installing the exact version of libssl that we need?

broken docker image nushell/nu:devel #646

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions