Publish to Docker Hub failing with "libcrypt.so.1: cannot open shared object file"

[simonw]

This means the Datasette 0.59.1 release has not been published to Docker Hub.

Here's where that failed: https://github.com/simonw/datasette/runs/3991043374?check_suite_focus=true

Preparing to unpack .../libc6_2.32-4_amd64.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Checking for services that may need to be restarted...
Checking init scripts...
Unpacking libc6:amd64 (2.32-4) over (2.28-10) ...
Setting up libc6:amd64 (2.32-4) ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
dpkg: error processing package libc6:amd64 (--configure):
 installed libc6:amd64 package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 libc6:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
The command '/bin/sh -c apt-get update &&     apt-get -y --no-install-recommends install software-properties-common &&     add-apt-repository "deb http://httpredir.debian.org/debian sid main" &&     apt-get update &&     apt-get -t sid install -y --no-install-recommends libsqlite3-mod-spatialite &&     apt-get remove -y software-properties-common &&     apt clean &&     rm -rf /var/lib/apt &&     rm -rf /var/lib/dpkg/info/*' returned a non-zero code: 100

Same problem when I attempted to publish using the "Push specific Docker tag" workflow: https://github.com/simonw/datasette/runs/3991059912?check_suite_focus=true

[simonw]

I can replicate locally by running:

docker build -f Dockerfile \
          -t datasetteproject/datasette:0.59.1 \
          --build-arg VERSION=0.59.1 .

This gives me the same error.

[simonw]

I got the same error publishing 0.59: https://github.com/simonw/datasette/actions/runs/1343251945

[simonw]

Right now the base image is:

datasette/Dockerfile

Line 1 in e6e4437

FROM python:3.9.2-slim-buster as build

I'm going to try python:3.9.7-slim-buster instead: https://hub.docker.com/layers/python/library/python/3.9.7-slim-buster/images/sha256-290b95e4b379762a9bd3d72644598e0972f4e2b5442bba60592c018fadcc744d?context=explore

[simonw]

Same errors with 3.9.7:

#5 41.46 /usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
#5 41.46 dpkg: error processing package libc6:amd64 (--configure):
#5 41.46  installed libc6:amd64 package post-installation script subprocess returned error exit status 127
#5 41.47 Errors were encountered while processing:
#5 41.47  libc6:amd64
#5 41.50 E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm suspicious of this part of the Dockerfile:

datasette/Dockerfile

Lines 1 to 18 in e6e4437

	FROM python:3.9.2-slim-buster as build
	# Version of Datasette to install, e.g. 0.55
	# docker build . -t datasette --build-arg VERSION=0.55
	ARG VERSION
	# software-properties-common provides add-apt-repository
	# which we need in order to install a more recent release
	# of libsqlite3-mod-spatialite from the sid distribution
	RUN apt-get update && \
	apt-get -y --no-install-recommends install software-properties-common && \
	add-apt-repository "deb http://httpredir.debian.org/debian sid main" && \
	apt-get update && \
	apt-get -t sid install -y --no-install-recommends libsqlite3-mod-spatialite && \
	apt-get remove -y software-properties-common && \
	apt clean && \
	rm -rf /var/lib/apt && \
	rm -rf /var/lib/dpkg/info/*

[simonw]

Looks like it's this bug, reported on the Debian mailing list: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1818037.html

No obvious workaround there though.

[simonw]

Here that is in the Debian bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993755

[simonw]

I think the root cause here is that I'm using a Debian Buster base image and then installing SpatiaLite from Debian unstable (sid) - as described in this comment: #1249 (comment)

That's has worked fine in the past, but Sid is unstable - and this seems to be one of those instabilities.

[simonw]

Debian stable these days is "bullseye" - https://www.debian.org/releases/ - which has the version of SpatiaLite that I was previously pulling in from Sid: https://packages.debian.org/bullseye/libsqlite3-mod-spatialite

So upgrading to the 3.9.7-slim-bullseye base image may help.

https://hub.docker.com/layers/python/library/python/3.9.7-slim-bullseye/images/sha256-67af5f544115124dc6d6da1d9d2815aa9825f6fd4aa6710adb0ec1725280fb89?context=explore

[simonw]

That fixed it! Resulting image is 249MB which is a very slight size reduction (I think previous was 259MB (uncompressed).

[simonw]

I'm going to attempt to publish 0.59 to Docker Hub using https://github.com/simonw/datasette/blob/2c31d1cd9cd3b63458ccbe391866499fa3f44978/.github/workflows/push_docker_tag.yml - if that works I'll push 0.59.1 as well.

[simonw]

That worked: https://hub.docker.com/layers/datasetteproject/datasette/0.59/images/sha256-038decc28e0ea84b281ecc0058fe8eba7aa99596e5a2177ff714092ad03294ed?context=explore