e3b9fbd6ba
Right now, the expectation for adding unpackaged content in a custom base image flow is to do it after the main compose. The problem however is that sometimes you want that content to affect the main compose itself, so doing it afterwards is not sufficient. The primary use case for this is sysusers.d dropins where you need to make sure that sysusers in scriptlets don't pick UIDs/GIDs already reserved on target client systems. One way to work around this is to synthesize an RPM that ships the dropin, and then ensure that it somehow runs as early as possible in the transaction. This is doable but obviously quite a hack. Enable this instead by adding a generic `--add-dir` switch which then just translates to `ostree-layers` in the override manifest. The dnf equivalent would be to first install e.g. `filesystem` and `setup`, add files to the rootfs, and then install all the other packages. See also discussions in https://github.com/coreos/rpm-ostree/pull/5354. |
||
|---|---|---|
| .tekton | ||
| fedora-includes | ||
| iot | ||
| minimal | ||
| minimal-plus | ||
| standard | ||
| tests | ||
| .gitlab-ci.yml | ||
| .mdl_style.rb | ||
| .mdlrc | ||
| .pre-commit-config.yaml | ||
| bootc-base-imagectl | ||
| bootc-base-imagectl.md | ||
| Containerfile | ||
| COPYING | ||
| fedora-40.yaml | ||
| fedora-41.yaml | ||
| fedora-42.yaml | ||
| fedora-bootc-config.json | ||
| fedora-bootc.yaml | ||
| fedora-iot.yaml | ||
| fedora-minimal-plus.yaml | ||
| fedora-minimal.yaml | ||
| fedora-rawhide.yaml | ||
| fedora-standard.yaml | ||
| fedora.repo | ||
| install-manifests | ||
| LICENSE | ||
| README.md | ||
| renovate.json | ||
Fedora bootc base images
Create and maintain base bootable container images from Fedora packages.
Motivation
The original Docker container model of using "layers" to model applications has been extremely successful. This project aims to apply the same technique for bootable host systems - using standard OCI/Docker containers as a transport and delivery format for base operating system updates.
Building images
The current default user experience is to build layered images on top of the official binary base images produced and tested by this project. See the documentation5 for more info.
You can build custom base images by forking this repository; however, https://gitlab.com/fedora/bootc/tracker/-/issues/32 tracks a more supportable mechanism that is not simply forking. For more information see6.
Build process
Building the images in this repo can be done with podman build, but
note the build process uses a special podman-ecosystem specific mechanism
to create fully custom images while inside a Containerfile.
You need to enable some privileges as nested containerization is required.
podman build --security-opt=label=disable --cap-add=all \
--device /dev/fuse -t localhost/fedora-bootc .
See the Containerfile for more details. This builds the default standard image.
Fedora versions
By default, the base images are built for Fedora rawhide. To build against a
different Fedora version, you can override the FROM image used to obtain the
Fedora repos and dnf variables. E.g.:
podman build --from quay.io/fedora/fedora:41 ...
Deriving
You are of course also free to fork, customize, and build base images yourself. See this page6 of the documentation for more information.
Tiers
At the current time, there is just one reference base image published to the registry. Internally the content set is split up somewhat into "tiers", but this is an internal implementation detail and may change at any time.
It is planned to rework and improve this in the future, especially to support smaller custom images. For more on this, see this tracker issue.
- standard: This image is the default, what is published as https://quay.io/repository/fedora/fedora-bootc
- minimal: This content set is more of a convenient centralization point for CI and curation around a package set that is intended as a starting point for a container base image.
- minimal-plus: This content set is intended to be the shared base used by all image-based Fedora variants (IoT, Atomic Desktops, and CoreOS).
standard inherits from minimal-plus and minimal-plus in turn inherit from minimal.
All non-trivial changes to minimal and minimal-plus should be ACKed by at least one stakeholder of each Fedora variant WGs.
Available Tiers + Versions
NOTE: The location and naming of these images is subject to change.
| Version | standard | minimal | minimal-plus |
|---|---|---|---|
| Rawhide | quay.io/fedora-testing/fedora-bootc:rawhide-standard | quay.io/fedora-testing/fedora-bootc:rawhide-minimal | quay.io/fedora-testing/fedora-bootc:rawhide-minimal-plus |
| Fedora 42 | quay.io/fedora-testing/fedora-bootc:42-standard | quay.io/fedora-testing/fedora-bootc:42-minimal | quay.io/fedora-testing/fedora-bootc:42-minimal-plus |
More information
Documentation: https://docs.fedoraproject.org/en-US/bootc/
Badges
| Badge | Description | Service |
|---|---|---|
 |
Dependencies | Renovate |
 |
Static quality gates | pre-commit |