BOOTC-INST...-FILESYSTEM(8)

💖 bootc-install-to-filesystem — the girlies' guide to installing onto a filesystem you already made 💖

okay so this is a section 8 manual page, from the System Manager's Manual, and it's literally just called bootc-install-to-filesystem. she does what she says on the tin, bestie. no cap. ✨

---

🌸 NAME 🌸

bootc-install-to-filesystem — install the system onto a filesystem structure that somebody else already set up for you 💅

---

🌈 SYNOPSIS 🌈

bootc install to-filesystem [OPTIONS...] <ROOT_PATH>

---

✨ DESCRIPTION ✨

Okay so picture this: you're installing, but you are NOT the one building the filesystem. This variant of installation is the "someone else already did the prep work" situation. 🫶

The root filesystem, plus any platform partitions that need to exist along the way (think the EFI system partition, that kind of thing), are prepared and mounted by an external tool or script. That's their job, not bootc's. And heads up — the root filesystem is currently expected to be empty by default. Empty empty. Like a fresh notebook. 🎀

girlies. say it with me. an external tool does the mounting. bootc does the installing. team effort. 🧚

---

👑 OPTIONS 👑

• ROOT_PATH — the path to the mounted root filesystem. that's the one you're installing onto. this argument is required, so like, don't forget her. 🙈
• --root-mount-spec=ROOT_MOUNT_SPEC — the source device specification for the root filesystem. for example, UUID=2e9f4241-229b-4202-8429-62d2302382e1. if you don't pass this one, the UUID of the target filesystem gets used instead. it exists as an option because some use cases might lowkey prefer mounting by a label instead, via e.g. LABEL=rootfs 💫
• --boot-mount-spec=BOOT_MOUNT_SPEC — the mount specification for the /boot filesystem 🌸
• --replace=REPLACE — initialize the system in-place. rn, only one mode for this is actually implemented. in the future it may also be supported to set up an explicit "dual boot" system 👀

possible values:

• wipe
• alongside

• --acknowledge-destructive — if the target IS the running system's root filesystem, this will skip any warnings. yes, past the warning sign, straight into it. she said she knows. 💀
• --skip-finalize — the default mode is to "finalize" the target filesystem by invoking fstrim and similar operations, and finally mounting it readonly. this option skips those operations. and when you skip them, it becomes the responsibility of the invoking code to perform those operations. so like, you're on your own for that part, beloved 🫠
• --source-imgref=SOURCE_IMGREF — install the system from an explicitly given source ⭐
• --target-transport=TARGET_TRANSPORT — the transport; e.g. oci, oci-archive, containers-storage. defaults to registry

default: registry

• --target-imgref=TARGET_IMGREF — specify the image to fetch for subsequent updates 🔥
• --enforce-container-sigpolicy — this is the inverse of the previous --target-no-signature-verification (which is now a no-op, rip). enabling this option enforces that containers-policy.json — see man containers-policy.json for the full search path — includes a default policy which requires signatures. we love a signed situation 💅
• --run-fetch-check — verify the image can be fetched from the bootc image. updates may fail when the installation host is authenticated with the registry but the pull secret is not in the bootc image 👑
• --skip-fetch-check — verify the image can be fetched from the bootc image. updates may fail when the installation host is authenticated with the registry but the pull secret is not in the bootc image 😭
• --disable-selinux — disable SELinux in the target (installed) system 🙈
• --karg=KARG — add a kernel argument. this option can be provided multiple times 🌈
• --karg-delete=KARG_DELETE — remove a kernel argument. this option can be provided multiple times 🍓
• --root-ssh-authorized-keys=ROOT_SSH_AUTHORIZED_KEYS — the path to an authorized_keys that will be injected into the root account 🔑
• --generic-image — perform configuration changes suitable for a "generic" disk image. at the moment: 💫
• --bound-images=BOUND_IMAGES — how should logically bound images be retrieved 🦋

possible values:

• stored
• skip
• pull

default: stored

• --stateroot=STATEROOT — the stateroot name to use. defaults to default 🌸
• --bootupd-skip-boot-uuid — don't pass --write-uuid to bootupd during bootloader installation 🚫
• --bootloader=BOOTLOADER — the bootloader to use 👢

possible values:

• grub
• grub-cc
• systemd
• none

• --composefs-backend — use the composefs backend instead of ostree. this is the default for images with a UKI, and for images with /usr/lib/composefs/setup-root-conf.toml and no ostree prepare-root.conf 🧚

default: false

• --allow-missing-verity — make fs-verity validation optional in case the filesystem doesn't support it (composefs backend only) 💜

default: false

• --uki-addon=UKI_ADDON — name of the UKI addons to install without the .efi.addon suffix. this option can be provided multiple times if multiple addons are to be installed (composefs backend only) ⭐

---

🎀 VERSION 🎀

v1.17.1

---

okay that's the whole page, we ate and left no crumbs 👑

this was the BOOTC-INST...-FILESYSTEM(8) page, printed straight out of the System Manager's Manual, and she is sitting pretty at version v1.17.1. mwah. periodt. 💖✨