bootc-install-to-filesystem - Man Page
Install to the target filesystem
Synopsis
bootc-install-to-filesystem [--root-mount-spec] [--root-options] [--boot-mount-spec] [--replace] [--target-transport] [--target-imgref] [--target-no-signature-verification] [--target-ostree-remote] [--skip-fetch-check] [--disable-selinux] [--karg] [-h|--help] [-V|--version] <ROOT_PATH>
Description
Install to the target filesystem
Options
- --root-mount-spec=ROOT_MOUNT_SPEC
Source device specification for the root filesystem. For example, UUID=2e9f4241-229b-4202-8429-62d2302382e1
- --root-options=ROOT_OPTIONS
Comma-separated mount options for the root filesystem. For example: rw,prjquota
- --boot-mount-spec=BOOT_MOUNT_SPEC
Mount specification for the /boot filesystem.
At the current time, a separate /boot is required. This restriction will be lifted in future versions. If not specified, the filesystem UUID will be used.
- --replace=REPLACE
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: Completely wipe the contents of the target filesystem. This cannot be done if the target filesystem is the one the system is booted from
- alongside: This is a destructive operation in the sense that the bootloader state will have its contents wiped and replaced. However, the running system (and all files) will remain in place until reboot
- --target-transport=TARGET_TRANSPORT [default: registry]
The transport; e.g. oci, oci-archive. Defaults to `registry`
- --target-imgref=TARGET_IMGREF
Specify the image to fetch for subsequent updates
- --target-no-signature-verification
Explicitly opt-out of requiring any form of signature verification
- --target-ostree-remote=TARGET_OSTREE_REMOTE
Enable verification via an ostree remote
- --skip-fetch-check
By default, the accessiblity of the target image will be verified (just the manifest will be fetched). Specifying this option suppresses the check; use this when you know the issues it might find are addressed.
Two main reasons this might fail:
- Forgetting `--target-no-signature-verification` if needed - Using a registry which requires authentication, but not embedding the pull secret in the image.
- --disable-selinux
Disable SELinux in the target (installed) system.
This is currently necessary to install *from* a system with SELinux disabled but where the target does have SELinux enabled.
- --karg=KARG
Add a kernel argument
- -h, --help
Print help (see a summary with '-h')
- -V, --version
Print version
- <ROOT_PATH>
Path to the mounted root filesystem.
By default, the filesystem UUID will be discovered and used for mounting. To override this, use `--root-mount-spec`.
Version
v0.1.0