docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
233 stars 48 forks source link

Why can't I update python:3.10-bullseye from dockerhub? #2350

Open ponponon opened 8 months ago

ponponon commented 8 months ago

I want to update python:3.10-bullseye from dockerhub

╰─➤  docker image ls | grep python
python        3.10-bullseye                  c05c608cfa20   24 months ago   915MB

There is A python:3.10-bullseye pulled two years ago on machine A. Now I have checked a python:3.10-bullseye in which the python interpreter version is python3.10.0, which is already very backward. I want to continue using python:3.10-bullseye, but update the python interpreter version from Python 3.10.0 to the latest Python 3.10.13

╰─➤  docker run --rm -it python:3.10-bullseye python --version 
Python 3.10.0

At this point, I run docker pull python:3.10-bullseye.

╰─➤  docker pull python:3.10-bullseye                                                                                                                                                                                                                                                                                127 ↵
3.10-bullseye: Pulling from library/python
Digest: sha256:fc1a412bab02c65978ad1cdc4ad3529d00886c9997d928bb9d6811b1198b72dc
Status: Image is up to date for python:3.10-bullseye
docker.io/library/python:3.10-bullseye

But the result was outrageous. After executing the pull command, the output log actually told me that my image was already up to date! However, this image is from two years ago, so it cannot be the latest in any case.

So I switched to a different machine B, a virgin machine that hadn't pulled python:3.10-bullseye before

─➤  docker pull python:3.10-bullseye           
3.10-bullseye: Pulling from library/python
ddf874abf16c: Pull complete 
5c1459d3ab8b: Pull complete 
29ab00e7798a: Pull complete 
7883a473306c: Pull complete 
c3ab175b762c: Pull complete 
9f11cb399571: Pull complete 
cfb416449119: Pull complete 
1365a3c2b71e: Pull complete 
Digest: sha256:e917e3e93525f97fc343135efc2b3295a11b02450ff8d4eeaff25323c73caf6b
Status: Downloaded newer image for python:3.10-bullseye
docker.io/library/python:3.10-bullseye

As you can see, on the new machine B, the python inside this python:3.10-bullseye is the latest Python 3.10.13

╰─➤  docker run --rm -it python:3.10-bullseye python --version 
Python 3.10.13

Why can't I update pyhon3.10-bullseye to the latest version on the original machine A? I wish to change the python interpreter in pyhon3.10-bullseye from python3.10.0 to python3.10.13.

milosgajdos commented 8 months ago

This isn't a Docker Hub question - this has to do with the runtime and how the runtime registry client checks for manifests before it attempts a PULL. I recommend asking in https://github.com/moby/moby.