• Describe the issue
  We currently have 2 differents process to release the Fedora Container Base image.

1 - To release the images on Docker Hub (@cverna responsible)
2 - To release the images on registry.fp.o and quay.io (@releng responsible)

I would like to merge the 2 processes into one to make it easier and stop needing to ping 2 people to release the images. Docker Hub has it's own way of doing things but both processes share a good common base.

The merged process would be as follow :

1 - Get the latest container compose for a specified tag (ie f29)
2 - Download the artifacts from the koji tasks
3 - For registry.fp.o and quay.io.
3.1 push each arch images to the registry (ie fedora:29-aarch64)
3.2 generate manifest list with all the arches
3.3 push the manifest list to the correct tags (ie fedora:latest, fedora:29)
4 - For Docker Hub
4.1 create a temporary workspace for each arch (ie workspace-29/aarch64)
4.2 extract the layer.tar from the archive into the workspace
4.3 Update the Dockerfile template with the name of the layer.tar
4.4 Clone https://github.com/fedora-cloud/docker-brew-fedora
4.5 Add and commit new files (Dockerfile and layer.tar) to the correct branch (ie 29)
4.6 Push to github
4.7 Update https://github.com/fedora-cloud/official-images/blob/master/library/fedora
4.8 Create a Pull Request

I have most (4.7 and 4.8 are not yet automated) of the Docker Hub process automated in a Python Script (https://pagure.io/docker-image-release/blob/master/f/tasks.py). And the releng process is scripted (https://pagure.io/releng/blob/master/f/scripts/sync-latest-container-base-image.sh).

I would like to merge these 2 scripts and see if we can make the container release process more available to people that are interested to help (For example Container SIG members). One possibility is to have this run in the infra OpenShift instance for example.

I am requesting feedback from the @releng group on these ideas ?

• When do you need this? (YYYY/MM/DD)

• When is this no longer needed or useful? (YYYY/MM/DD)

• If we cannot complete your request, what is the impact?