Fedora latest tag pointing to older image

[siddharthvipul]

I have a merged PR to point the latest tag to a newer image (version 32). On the docker hub website Fedora readme, it's correctly showing version 32 is the latest. But when pulling using docker pull fedora:latest it pulls 31.
I tried pulling version 32 by itself and it works as expected (pulled f32).

I see different digests for 32 and latest tags on dockerhub f32 vs latest

Do I have to update something else other than already udpated tag?

[siddharthvipul]

also (not sure if's relevant), https://download.docker.com/linux/fedora/ has no f32 directory,
Is there something I can do to update it there? :)
apologies if these are too obvious... I have recently started doing this

[wglambert]

There's an open PR for this issue #8164

You can pull fedora:32 in the meantime

[raveit65]

You can pull fedora:32 in the meantime

Thanks but not practicable.
We (Mate desktop) are using fedora docker images for a lot of repos with different branches at github with Travis CI.
https://github.com/mate-desktop
The idea of the latest tag is not to change our configs every 6 months.
Ok, we have to wait...

[tianon]

Arg, #8240 has suffered from docker-library/bashbrew#8.

We wouldn't have run into this issue if #8164 had been merged instead (since it would've then rebuilt fedora:32). I'll see if I can update it by hand instead.

also (not sure if's relevant), https://download.docker.com/linux/fedora/ has no f32 directory,

That's not something we're involved with -- looking at https://github.com/docker/docker-ce-packaging, it appears to have been added in docker/docker-ce-packaging@b6331a2, so it's probably just waiting for the next (major) release of Docker (cc @thaJeztah).

[tianon]

This is now fixed: docker-library/repo-info@664c661

[raveit65]

I can confirm that the issue is fixed and fedora 32 is used with our Travis CI builds.
From today:
https://travis-ci.org/github/mate-desktop/mate-terminal/jobs/706084787#L213

Thanks a lot for fixing this.