Hi @ralph, which image do you expect to pull when pulling from the 'latest' tag?
Rawhide? Latest released fedora?
Looking at our registries we do have the latest tag in registry.fp.org but the image is older than rawhide.

We should publish the images consistently, so all registries we use are interchangeable.

Oh, I would expect the latest GA release - whatever that is: rawhide - 1.

This needs updates to https://pagure.io/releng/blob/master/f/scripts/sync-latest-container-base-image.sh script

@mohanboddu, there already is this line that is supposed to copy the image to quay.io/fedora/fedora:latest

How and where is this script executed? it may be just a question of changing parameters to the script.

@mohanboddu, there already is this line that is supposed to copy the image to quay.io/fedora/fedora:latest

This is not correct, it is being set by this code which only handle registry.fp.o and candidate-registry.fp.o but not quay.io.

How and where is this script executed? it may be just a question of changing parameters to the script.

You can login in compose-rawhide01.iad2.fp.o and run the script as root with a release number, ex for rawhide:

# ./sync-latest-container-base-image.sh 34

So in order to support multi arch we need the latest tag to be a manifest list, which was not supported until recently in quay.io.

Not long ago I pushed https://pagure.io/releng/c/0b3e9d5a53162245635e07b6f7e9b3a008da05cd?branch=master which make this happened but that also broke registry.fp.o for some reasons :( so I reverted it back.

I think a good way forward is to probably have use podman to generate the manifest list only for quay.io and leave the current method for registry.fp.o

Let me know if that makes sense or not :P

I am okay with it, we need to look at how to generate the manifest list with podman as I have no idea about it.