quay.io images out of date compared to docker hub

[daniel-j-h]

Hey folks, checking out your documentation you seem to provide container images on both docker hub as well as on quay.io

• https://hub.docker.com/_/almalinux/tags
• https://quay.io/repository/almalinux/almalinux?tab=info

If I check out the quay.io registry I can see the last activity in there was in 2022.

Can we assume that quay.io is no longer a supported registry here and should we then remove it from all documentation and websites?

[yuravk]

Please check the https://quay.io/repository/almalinuxorg/almalinux repository.

[daniel-j-h]

Interesting - so there are two

• https://quay.io/repository/almalinuxorg/almalinux <- the one you linked
• https://quay.io/repository/almalinux/almalinux <- the one that was previously announced and used

Is there a reason for this change and was this announced somewhere? Back then in the original announcements you can see how it's pointing to the now outdated quay repository

• https://almalinux.org/blog/minimal-container-images-now-available-on-docker-hub-and-quay-io/
• https://forums.almalinux.org/t/minimal-container-images-now-available-on-docker-hub-and-quay-io/323

Should the old quay repository or even the whole organization then be deleted or otherwise deprecated? Everyone who set up this original quay repository and hasn't changed to the new one will not get any updates and run almost two year old containers.

[codyro]

Is there a reason for this change, and was this announced somewhere?

I believe the individual who initially set up this account was/is unreachable, so it was decided to create a new one for the organization. It was not announced anywhere AFAIK.

We should try to get this resolved, as it's confusing.

EDIT There is also a warning on the wiki to help warn users to ensure they're using the right one. That, alongside @sboldyreva's changes, should be sufficient.

[sboldyreva]

@daniel-j-h Thanks for bringing this up! I've checked our blog and wiki for mentioning the incorrect quay.io links and updated them to avoid any further misinformation :)

[sboldyreva]

@codyro the warning just appeared today thanks to this issue report, I put just for extra attention

[codyro]

@codyro the warning just appeared today thanks to this issue report, I put just for extra attention

Andrew just told me in chat. I'm clearly not on top of it today 😅

[nate-duke]

FYI that old repo is still there. Is there a way to redirect to an appropriate place or otherwise non-disruptively remove it?