Split out postprocess-conf.yaml

Prep for working on custom base images. We want to support
operating on rootfs that may not have been generated by
rpm-ostree.

Split this out as something that can gets passed separately
to `rpm-ostree compose postprocess/commit`.
This commit is contained in:
Colin Walters 2025-01-13 09:21:26 -05:00
parent edac3c53ca
commit 535cea4155
3 changed files with 36 additions and 32 deletions

View File

@ -1,40 +1,12 @@
edition: "2024" edition: "2024"
# https://github.com/CentOS/centos-bootc/issues/167
machineid-compat: true
# Be minimal # Be minimal
recommends: false recommends: false
ignore-removed-users:
- root
ignore-removed-groups:
- root
etc-group-members:
- wheel
- sudo
- systemd-journal
- adm
# Default to `bash` in our container, the same as other containers we ship. # Default to `bash` in our container, the same as other containers we ship.
container-cmd: container-cmd:
- /sbin/init - /sbin/init
# Note that the default for c9s+ is sqlite; we can't rely on rpm being
# in the target (it isn't in tier-0!) so turn this to host here. This
# does break the "hermetic build" aspect a bit. Maybe eventually
# what we should do is special case this and actually install RPM temporarily
# and then remove it...
rpmdb: host
check-passwd:
type: "file"
filename: "passwd"
check-groups:
type: "file"
filename: "group"
automatic-version-prefix: "${releasever}.<date:%Y%m%d>"
mutate-os-release: "${releasever}"
remove-from-packages: remove-from-packages:
# Generally we expect other tools to do this (e.g. Ignition or cloud-init) # Generally we expect other tools to do this (e.g. Ignition or cloud-init)
- [systemd, /usr/lib/systemd/system/sysinit.target.wants/systemd-firstboot.service] - [systemd, /usr/lib/systemd/system/sysinit.target.wants/systemd-firstboot.service]
@ -43,6 +15,7 @@ remove-from-packages:
- [systemd-udev, /usr/lib/systemd/system-generators/systemd-gpt-auto-generator] - [systemd-udev, /usr/lib/systemd/system-generators/systemd-gpt-auto-generator]
include: include:
- postprocess-conf.yaml
- bootc.yaml - bootc.yaml
- bootupd.yaml - bootupd.yaml
- ostree.yaml - ostree.yaml

View File

@ -1,9 +1,6 @@
packages: packages:
- ostree nss-altfiles - ostree nss-altfiles
# We want content lifecycled with the image
opt-usrlocal: "root"
postprocess: postprocess:
# Set up default root config # Set up default root config
- | - |

View File

@ -0,0 +1,34 @@
# This file configures things relevant to `rpm-ostree compose postprocess`.
# We want content lifecycled with the image
opt-usrlocal: "root"
# https://github.com/CentOS/centos-bootc/issues/167
machineid-compat: true
# Note that the default for c9s+ is sqlite; we can't rely on rpm being
# in the target (it isn't in tier-0!) so turn this to host here. This
# does break the "hermetic build" aspect a bit. Maybe eventually
# what we should do is special case this and actually install RPM temporarily
# and then remove it...
rpmdb: host
ignore-removed-users:
- root
ignore-removed-groups:
- root
etc-group-members:
- wheel
- sudo
- systemd-journal
- adm
check-passwd:
type: "file"
filename: "passwd"
check-groups:
type: "file"
filename: "group"
automatic-version-prefix: "${releasever}.<date:%Y%m%d>"
mutate-os-release: "${releasever}"