python3.7-nodejs14-slim tag is 3.7.10 not 3.7.11

[PaulMonnery]

Hi, thanks for these very usefull images!

I am currently facing an issue with the python3.7-nodejs14-slim tag. it is written on the README that the python version is 3.7.11 but it is in fact python 3.7.10, which breaks my poetry installation because of incompatible version with some packages 😬

$ docker run --rm -it nikolaik/python-nodejs:python3.7-nodejs14-slim python --version
Python 3.7.10

Is it a build step issue within the dockerfile or the readme is just not up to date?

EDIT: from python-nodejs:python3.7-nodejs16-slim, python version is indeed 3.7.11

[nikolaik]

Hi, thanks for these very usefull images!

I'm glad you find them useful! 🤗

I am currently facing an issue with the python3.7-nodejs14-slim tag. it is written on the README that the python version is 3.7.11 but it is in fact python 3.7.10, which breaks my poetry installation because of incompatible version with some packages 😬

$ docker run --rm -it nikolaik/python-nodejs:python3.7-nodejs14-slim python --version
Python 3.7.10

What version of python do you get if you run docker run --pull=always --rm -it nikolaik/python-nodejs:python3.7-nodejs14-slim python --version? It could simply be because you have pulled the tag when the image was at pthon 3.7.10 and need to do it again to get on the latest and greatest.

If you want to pin the python version, you probably want to create your own image, since the tags are constantly evolving with new bugfix releases of python. If you just need the latest. You can run docker pull once in a while or give a little present of --pull=always to docker run.

[PaulMonnery]

Running docker run --pull=always --rm -it nikolaik/python-nodejs:python3.7-nodejs14-slim python --version solved the problem, thanks!

Indeed, I will maybe have to build my own images if it breaks on each new release 🤔 I'll see on next release then!

[nikolaik]

Glad it worked out!