The :latest tag in fedoraproject is Fedora 37, but is 39 in quay
ianw opened this issue · 2 comments
The two versions appear to be out of sync. Is the registry.fedoraproject.org
updated any more? If not, should it be deleted to remove confusion?
$ podman run --dns=none -it registry.fedoraproject.org/fedora-toolbox:latest /bin/bash -c "cat /etc/os-release | grep VERSION_ID="
VERSION_ID=37
$ podman run --dns=none -it quay.io/fedora/fedora-toolbox:latest /bin/bash -c "cat /etc/os-release | grep VERSION_ID="
VERSION_ID=39
$ podman image ls --digests
REPOSITORY TAG DIGEST IMAGE ID CREATED SIZE
quay.io/fedora/fedora-toolbox latest sha256:80a1b6089056143996541bcb2a920aba42b1ea845c25a6ffb313af83367bfc0b 35f981983e47 2 weeks ago 1.04 GB
registry.fedoraproject.org/fedora-toolbox latest sha256:d3844264634e9ec24c19efbb3a03c8bd33064e26cdcd3dac2ce686bcfd363b37 4e66c5ceece9 2 weeks ago 999 MB
Just now I got:
[rishi@topinka ~]$ podman run --dns=none -it registry.fedoraproject.org/fedora-toolbox:latest /bin/bash -c "cat /etc/os-release | grep VERSION_ID="
Trying to pull registry.fedoraproject.org/fedora-toolbox:latest...
Getting image source signatures
Copying blob d377ca97e054 done |
Copying config e23f4a7692 done |
Writing manifest to image destination
VERSION_ID=39
Anyway, it doesn't matter.
The default and canonical location for the fedora-toolbox
images is registry.fedoraproject.org
. That's what's baked into the toolbox(1)
binary, and that's what's tested. From Fedora 39 onwards, these images are produced by Fedora's nightly composes.
The latest
tag is not used by default, because the version of the host is explicitly used by default. When the --release
option is used, it's also expected to be a numerical Fedora version. Only if someone uses the --image
option, then the latest
tag might be used.
There's an ongoing migration from registry.fedoraproject.org
to quay.io
that's being worked on for a while. Hopefully, some day it will get done. :)
Thanks for stopping by, and your recent work on Toolbx and it's ecosystem, @ianw !