Poetry downgrade breaking Python on p3.9/n12 about docker-python-nodejs

[ericboucher]

Hi @nikolaik, actually we realized that the issue happened after downgrading poetry. But don't understand why that would be happening.

So to replicate, simply run the following command in the docker:

poetry self update 1.1.8
python

We found a workaround, or rather just decided to up to 1.1.11, but are curious about what could be causing the issue. And prevent it from happening again in the future :)

[nikolaik]

Hi @ericboucher 👋

I cant seem to reproduce the issue. Are you doing something special with LD_LIBRARY_PATH or similar?

$ docker pull nikolaik/python-nodejs:python3.9-nodejs12
python3.9-nodejs12: Pulling from nikolaik/python-nodejs
Digest: sha256:9fce3e029314ac5ab30014d9962a54090bf600f73ba8398746fc76e17f50669c
Status: Image is up to date for nikolaik/python-nodejs:python3.9-nodejs12
$ docker run --rm -it --entrypoint bash nikolaik/python-nodejs:python3.9-nodejs12
root@e42995d68cae:/# cat /etc/ld.so.conf.d/libc.conf
# libc default configuration
/usr/local/lib
root@e42995d68cae:/# ls -la /usr/local/lib/libpython3.9.so.1.0
-rwxr-xr-x 1 root root 21505160 Oct 13 09:08 /usr/local/lib/libpython3.9.so.1.0
root@e42995d68cae:/# ldd /usr/local/lib/libpython3.9.so.1.0
	linux-vdso.so.1 (0x00007ffc18fa2000)
	libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007fefe70d2000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fefe70b1000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fefe70ac000)
	libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fefe70a7000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fefe6f24000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fefe6d63000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fefe74e0000)
root@e42995d68cae:/# python
Python 3.9.7 (default, Oct 13 2021, 09:08:19) 
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 

[nikolaik]

I'll close this for now, even though we never got to the root cause of your issue. If it pops up again in the future we can investigate further.