Koji uses Image Builder locally
Summary
Switch Image Builder-built images in Koji to not build through a service, but locally.
Owner
- Name: Simon de Vlieger
- Email: cmdr@supakeen.com or supakeen@redhat.com
- Targeted release: Fedora Linux 42
- Last updated: 2025-01-04
- [<link to devel-announce post will be added by Wrangler> Announced]
- [<will be assigned by the Wrangler> Discussion thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Several Fedora images are being built by the Image Builder service (Fedora IoT, Fedora Minimal). Image Builder acts as a content generator in Koji. Images are built external to Fedora infrastructure as requested by Koji and then delivered back.
This has led to of issues over time. Amongst them instability and the inability of Fedora release engineering and infrastructure teams to intervene and the inability to freeze the external infrastructure during a release window.
I plan to replace the current approach in koji-osbuild with a local-only build. Image Builder machinery and definitions will still be used for the mentioned images but the build will run locally on Fedora infrastructure and builders. In the same way that kiwi or livemediacreator-images are built.
Feedback
This change proposal does not yet provide a way for the distribution definitions to be owned by, and live inside, Fedora infrastructure. I plan to address this in a later change proposal.
Benefit to Fedora
Control over Image Builder on its own infrastructure, lessen remove the need to reach out to external parties when releases are blocked.
Scope
Proposal Owners
- Submit the
image-builder-clipackage for inclusion in Fedora 42. - Change the
koji-osbuildplugin to provide a new task type that usesimage-builder-cli; alternatively: provide a newkoji-image-builderplugin if that suits better. - Submit the above mentioned update to the koji plugin, or a new package for inclusion in Fedora 42.
- Install new packages on build machines.
- Changes to pungi to be able to schedule these tasks.
- Changes to pungi config for Fedora IoT.
- Changes to pungi config for Fedora Minimal.
Contingency Plan
Independent of where on the above tasks I get stuck we can continue to build with the currently available system.