.ds Aq \(aq
.nh
.TH NAME
bootc-install-config.toml


.SH DESCRIPTION
The \fBbootc install\fR process supports some basic customization.  This configuration file
is in TOML format, and will be discovered by the installation process in via "drop-in"
files in \fB/usr/lib/bootc/install\fR that are processed in alphanumerical order.

.PP
The individual files are merged into a single final installation config, so it is
supported for e.g. a container base image to provide a default root filesystem type,
that can be overridden in a derived container image.


.SH install
This is the only defined toplevel table.

.PP
The \fBinstall\fR section supports these subfields:
.IP \(bu 2
\fBblock\fR: An array of supported \fBto-disk\fR backends enabled by this base container image;
if not specified, this will just be \fBdirect\fR\&.  The only other supported value is \fBtpm2-luks\fR\&.
The first value specified will be the default.  To enable both, use \fBblock = ["direct", "tpm2-luks"]\fR\&.
.IP \(bu 2
\fBfilesystem\fR: See below.
.IP \(bu 2
\fBkargs\fR: An array of strings; this will be appended to the set of kernel arguments.
.IP \(bu 2
\fBmatch_architectures\fR: An array of strings; this filters the install config.
.IP \(bu 2
\fBostree\fR: See below.
.IP \(bu 2
\fBstateroot\fR: The stateroot name to use. Defaults to \fBdefault\fR\&.
.IP \(bu 2
\fBroot-mount-spec\fR: A string specifying the root filesystem mount specification.
For example, \fBUUID=2e9f4241-229b-4202-8429-62d2302382e1\fR or \fBLABEL=rootfs\fR\&.
If not provided, the UUID of the target filesystem will be used.
An empty string signals to omit boot mount kargs entirely.
.IP \(bu 2
\fBboot-mount-spec\fR: A string specifying the /boot filesystem mount specification.
If not provided and /boot is a separate mount, its UUID will be used.
An empty string signals to omit boot mount kargs entirely.


.SH filesystem
There is one valid field:
.IP \(bu 2
\fBroot\fR: An instance of "filesystem-root"; see below


.SH filesystem-root
There is one valid field:

.PP
\fBtype\fR: This can be any basic Linux filesystem with a \fBmkfs.$fstype\fR\&.  For example, \fBext4\fR, \fBxfs\fR, etc.


.SH ostree
Configuration options for the ostree repository. There is one valid field:
.IP \(bu 2
\fBbls-append-except-default\fR: A string of kernel arguments that will be appended to
Boot Loader Spec entries, except for the default entry. This is useful for configuring
arguments that should only apply to non-default deployments.


.SH bootupd
Configuration options for bootupd, responsible of setting up the bootloader.
There is only one valid field:
- \fBskip-boot-uuid\fR: A boolean that controls whether to skip writing partition UUIDs
   to the bootloader configuration. When \fBtrue\fR, bootupd is invoked with \fB--with-static-configs\fR
   instead of \fB--write-uuid\fR\&. Defaults to \fBfalse\fR (UUIDs are written by default).


.SH Examples
.EX
[install.filesystem.root]
type = "xfs"

[install]
kargs = ["nosmt", "console=tty0"]
stateroot = "myos"
root-mount-spec = "LABEL=rootfs"
boot-mount-spec = "UUID=abcd-1234"

[install.ostree]
bls-append-except-default = 'grub_users=""'
.EE


.SH SEE ALSO
\fBbootc(1)\fP


.SH VERSION
v1.15.0
