.ds Aq \(aq
.nh
.TH NAME
bootc-install-to-filesystem \- Install to an externally created
filesystem structure


.SH SYNOPSIS
\fBbootc install to-filesystem\fP [\fIOPTIONS...\fP] <\fIROOT_PATH\fP>


.SH DESCRIPTION
Install to an externally created filesystem structure.

.PP
In this variant of installation, the root filesystem alongside any
necessary platform partitions (such as the EFI system partition) are
prepared and mounted by an external tool or script. The root filesystem
is currently expected to be empty by default.


.SH OPTIONS
.PP
\fBROOT_PATH\fP

.EX
Path to the mounted root filesystem

This argument is required.
.EE

.PP
\fB--root-mount-spec\fP=\fIROOT_MOUNT_SPEC\fP

.EX
Source device specification for the root filesystem.  For example, `UUID=2e9f4241-229b-4202-8429-62d2302382e1`. If not provided, the UUID of the target filesystem will be used. This option is provided as some use cases might prefer to mount by a label instead via e.g. `LABEL=rootfs`
.EE

.PP
\fB--boot-mount-spec\fP=\fIBOOT_MOUNT_SPEC\fP

.EX
Mount specification for the /boot filesystem
.EE

.PP
\fB--replace\fP=\fIREPLACE\fP

.EX
Initialize the system in-place; at the moment, only one mode for this is implemented. In the future, it may also be supported to set up an explicit "dual boot" system

Possible values:
- wipe
- alongside
.EE

.PP
\fB--acknowledge-destructive\fP

.EX
If the target is the running system's root filesystem, this will skip any warnings
.EE

.PP
\fB--skip-finalize\fP

.EX
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.  It is then the responsibility of the invoking code to perform those operations
.EE

.PP
\fB--source-imgref\fP=\fISOURCE_IMGREF\fP

.EX
Install the system from an explicitly given source
.EE

.PP
\fB--target-transport\fP=\fITARGET_TRANSPORT\fP

.EX
The transport; e.g. oci, oci-archive, containers-storage.  Defaults to `registry`

Default: registry
.EE

.PP
\fB--target-imgref\fP=\fITARGET_IMGREF\fP

.EX
Specify the image to fetch for subsequent updates
.EE

.PP
\fB--enforce-container-sigpolicy\fP

.EX
This is the inverse of the previous `--target-no-signature-verification` (which is now a no-op).  Enabling this option enforces that `/etc/containers/policy.json` includes a default policy which requires signatures
.EE

.PP
\fB--run-fetch-check\fP

.EX
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
.EE

.PP
\fB--skip-fetch-check\fP

.EX
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
.EE

.PP
\fB--disable-selinux\fP

.EX
Disable SELinux in the target (installed) system
.EE

.PP
\fB--karg\fP=\fIKARG\fP

.EX
Add a kernel argument.  This option can be provided multiple times
.EE

.PP
\fB--karg-delete\fP=\fIKARG_DELETE\fP

.EX
Remove a kernel argument.  This option can be provided multiple times
.EE

.PP
\fB--root-ssh-authorized-keys\fP=\fIROOT_SSH_AUTHORIZED_KEYS\fP

.EX
The path to an `authorized_keys` that will be injected into the `root` account
.EE

.PP
\fB--generic-image\fP

.EX
Perform configuration changes suitable for a "generic" disk image. At the moment:
.EE

.PP
\fB--bound-images\fP=\fIBOUND_IMAGES\fP

.EX
How should logically bound images be retrieved

Possible values:
- stored
- skip
- pull

Default: stored
.EE

.PP
\fB--stateroot\fP=\fISTATEROOT\fP

.EX
The stateroot name to use. Defaults to `default`
.EE

.PP
\fB--bootupd-skip-boot-uuid\fP

.EX
Don't pass --write-uuid to bootupd during bootloader installation
.EE

.PP
\fB--bootloader\fP=\fIBOOTLOADER\fP

.EX
The bootloader to use

Possible values:
- grub
- systemd
- none
.EE

.PP
\fB--composefs-backend\fP

.EX
If true, composefs backend is used, else ostree backend is used

Default: false
.EE

.PP
\fB--allow-missing-verity\fP

.EX
Make fs-verity validation optional in case the filesystem doesn't support it

Default: false
.EE

.PP
\fB--uki-addon\fP=\fIUKI_ADDON\fP

.EX
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
.EE


.SH VERSION
v1.15.1
