BOOTC-INSTALL(8)
π NAME π
bootc-install β install the running container to a target, bestie. yes really, the whole container, we're turning it into a bootable system π
πΈ SYNOPSIS πΈ
bootc install [OPTIONS...] <SUBCOMMAND>
β¨ DESCRIPTION β¨
So like, bootc install takes the container you're running right now and installs it onto a target. That's the vibe. π«Ά
π¦ Understanding installations π¦
Okay this is the part where people get confused, so listen up. The bootc install flow turns a container image into a bootable system. And that means it handles the filesystem, the bootloader, and the update metadata setup. It is genuinely not just a copy of the container filesystem. Not even close. It's giving full system surgery π
If you want the whole installation model, the prereqs, and end-to-end examples, go read Installing bootc compatible images (see bootc-installation(7)). This page right here is just the reference for the command and its subcommands. iykyk π
π Secure Boot Keys π
When you're installing with systemd-boot, bootc can let systemd-boot handle the enrollment of Secure Boot keys. How? By putting signed EFI signature lists in /usr/lib/bootc/install/secureboot-keys, which will copy over into ESP/loader/keys after bootloader installation. Those keys get copied to the loader/keys subdirectory of the ESP, after installing systemd-boot to the system. Periodt. π
Want the deets on how key enrollment actually works with systemd-boot? It's all in the systemd-boot man page:
π SUBCOMMANDS π
Pick your fighter, bestie. Each one is a whole mood:
bootc install mountβ Mounts an installed deployment into a caller-owned directory. lowkey so useful πͺbootc install to-diskβ Installs to the target block device. straight to the disk, no detours πΎbootc install to-filesystemβ Installs to an externally created filesystem structure. you bring the filesystem, it brings the install β¨bootc install to-existing-rootβ Installs to the host root filesystem. it's giving "move in, I already live here" πbootc install finalizeβ Execute this as the penultimate step of an installation usinginstall to-filesystem. the second-to-last step, the opening act before the finale π¬bootc install ensure-completionβ Intended for use in environments that are performing anostree-based installation, not bootc. read that again fr fr πbootc install print-configurationβ Outputs JSON tostdoutthat contains the merged installation configuration, as it may be relevant to calling processes usinginstall to-filesystemthat in particular want to discover the desired root filesystem type from the container image. yes it's a long one, it's doing a lot ποΈ
β VERSION β
v1.17.1 β that's the one you're running, no cap π
okay that's the whole page babes π this was bootc-install(8), a System Manager's Manual situation, version v1.17.1, and you read the whole thing which means you're officially built different πβ¨π¦ go install something iconic π
π¦ where this page comes from
- fedora 43: bootc 1.17.1-1.fc43 Β· Apache-2.0 AND BSD-3-Clause AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (Unlicense OR MIT)
- fedora 44: bootc 1.17.1-1.fc44 Β· Apache-2.0 AND BSD-3-Clause AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (Unlicense OR MIT)
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms