2.6 KiB
Trying out development builds
nav_order: 2
Rebasing from Fedora CoreOS
Fedora CoreOS supports many different platforms, and can be used as a starting point to "rebase" to a custom derived image from CentOS boot.
systemctl mask --now zincati && rm -vf /run/ostree/staged-deployment-locked
echo "# dummy change" >> "/etc/sudoers.d/coreos-sudo-group"
rpm-ostree rebase ostree-unverified-registry:quay.io/centos-boot/fedora-tier-1:eln
systemctl reboot
See also this pull request for more information.
TODO: Use osbuild
Document the ongoing work to materialize a disk image from a container.
Using bootc install-to-filesystem --replace=alongside with a cloud image
A toplevel goal of this project is that the "source of truth" for Linux operating system management is a container image registry - as opposed to e.g. a set of qcow2 OpenStack images or AMIs, etc.
The latest development builds of bootc have support for
bootc install-to-filesystem --replace=alongside. More about this core
mechanic in the bootc install docs.
Here's an example set of steps to execute; this could be done via e.g. cloud-init configuration.
dnf -y install podman skopeo
podman run --rm --privileged --pid=host -v /:/target --security-opt label=type:unconfined_t quay.io/centos-boot/fedora-tier-1:eln bootc install-to-filesystem --target-no-signature-verification --karg=console=ttyS0,115200n8 --replace=alongside /target
reboot
Generating a derived container image
These examples just use a "stock" container image, and in the first case rely on
user state being preserved by the rpm-ostree rebase.
What's much more interesting is to generate a custom derived container image, and target that instead. For more information, see