Missing builds for Python 3.14

[samypr100]

Some tags have layers, while others are missing.

For example python:3.14.0 missing vs python:trixie properly points to 3.14.

After merging #20035 the meta repo got the corresponding changes in docker-library/meta@f74572c and the staging builds started and finished in jenkins. I did not see any Jenkins build failures, but may have missed something.

Once the jenkins builds finished the builds.json got generated in docker-library/meta@ed18468 with the appropriate references to oisupport/staging.

Is there something else that can be causing an issue?

[zanieb]

cc @yosifkit

[samypr100]

Example for 3.14

$ docker run -it docker.io/python:3.14.0
Unable to find image 'python:3.14.0' locally
3.14.0: Pulling from library/python
docker: no matching manifest for linux/amd64 in the manifest list entries

$ docker run -it docker.io/python:3.14
Unable to find image 'python:3.14' locally
3.14: Pulling from library/python
docker: no matching manifest for linux/amd64 in the manifest list entries

$ docker run -it docker.io/python:trixie
Python 3.14.0 (main, Oct  7 2025, 20:52:42) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

Many of the shared tags for 3.13 also point to 3.13.7 rather than 3.13.8.

$ docker run -it docker.io/python:3.13.8
Unable to find image 'python:3.13.8' locally
3.13.8: Pulling from library/python
docker: no matching manifest for linux/amd64 in the manifest list entries

$ docker run -it docker.io/python:3.13
Python 3.13.7 (main, Sep 30 2025, 10:24:57) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

$ docker run -it docker.io/python:bookworm
Python 3.13.7 (main, Sep 30 2025, 10:24:26) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

[zanieb]

astral-sh/uv#16150 (comment) seems relevant

[samypr100]

astral-sh/uv#16150 (comment) seems relevant

I guess the question is do the riscv64 and ppc64le jobs need to finish for this issue to be fixed for other architectures?

[yosifkit]

Is there something else that can be causing an issue?

After those parts you describe, the build is pushed into the arch-specific namespaces (like https://hub.docker.com/r/amd64/python) via the deploy jobs and then a separate job (put-shared) combines whatever is available from those arch-specific namespaces into the image index for python (aka library/python). I've gone ahead and triggered the put shared for python and it looks like everything but riscv64 is there now.

[samypr100]

Thanks @yosifkit, I was not patient enough 😅

[zanieb]

Thank you! That unblocks us over in uv :)