Fedora Base/Minimal/CoreOS container images
This document contains information about current workflow used to build and publish these container images. It also describes changes needed to make it work with quay.io.
The base/minimal/CoreOS images are currently built using OSBS. The OSBS submits builds to candidate-registry.fedoraproject.org using dockercfg and user can create an update in Bodhi. After testing period is finished or the update gets enough karma it is moved by bodhi to registry.fedoraproject_org.
Changes for quay.io
This section will describe changes that are needed to make quay.io work with current setup. It will go through pipeline step by step and describe what needs to be changed in case of base/minimal/CoreOS images workflow.
OSBS is using Openshift local container registry, which is configured by dockercfg file and pointing to candidate-registry. There is dockercfg for production and staging. This dockercfg is used as a secret in OSBS and it’s deployed in setup-worker-namespace playbook. To make this work with quay.io we need to replace the dockercfg with new one pointing to quay.io.
OSBS could have trouble reaching to quay.io, this needs to be solved for this to work.
In the new workflow introduced in Fedora 39+ is a Release Engineering script that pushes the image to registry. This script could be found in releng repository and it’s already pushing images to quay.io.
To make it work with quay.io we just need to change container.destination_registry and container.source_registry variables.
Bodhi wouldn’t be part of the base/minimal/CoreOS images workflow in Fedora 39 and later.So no need to change anything here.