Release the Fedora Container Base Image


This SOP covers the steps involved in changing and releasing the Fedora Container Base image.

Fedora releases 2 container base images, fedora and fedora-minimal. These images are available on 3 registries, and DockerHub (fedora-minimal is not available in DockerHub).

Modify a base image (Kickstart)

Base images are built in koji using the image-factory application to build the container image root filesystem (rootfs). Kickstart files are used to configure how the image is built and what is available in the image The solution consist of 3 Kickstarts.




Changes made on the rawhide branch will results in the rawhide image, other branches (f30, f31) should be used to modify other releases.

Compose Configuration (Pungi)

The configuration used to compose the container images is available in the pungi-fedora repository.

For rawhide the configuration is in

While for other releases the configuration is in a dedicated file

Release on and

If you want to release the base image on registry.fp.o and you can use the following script.

You will need to run that script from on of the releng composer machines in the infrastructure in order to have the credentials.

If you do not have access to that machines, you can request the release by opening a ticket on the releng tracker.

The script can then be executed as follow

$./ 31
$./ 32

This will take care of pushing the fedora and fedora-minimal images to both registries.

Release on DockerHub

Releasing on DockerHub is a little different since Fedora is an “offical” image there. In order to release new images there we have to update a Dockerfile and rootfs tarball on the following repo.


For the details on how to run the script please see