bootc

You can use the bootc command to install a system from a native bootable container image. Use this command to specify the source container image, the target image for future updates, and the stateroot for the installation. You can use the following Kickstart commands:

  • clearpart, zerombr
  • bootloader (only the --append option)
  • autopart, reqpart, part, volgroup, logvol
  • reboot, halt, poweroffgraphical, cmdline, text, rdp
  • %pre, %post, %include
  • keyboard
  • lang
  • network
  • rhsm
  • rootpw
  • sshkey
  • timezone
  • user
Important

bootc is provided as a Technology Preview only. Technology Preview features are not supported with Red Hat production Service Level Agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These previews provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.
Syntax
# bootc [--stateroot STATEROOT] --source-imgref SOURCEIMGREF [--target-imgref TARGETIMGREF]
Options
  • --stateroot: Defines the name of the state directory, which is also referred to as the osname.
  • --source-imgref: Specifies the explicit source location from which the system is installed. It must be specified in <transport>:<image-url> format, for example, registry:registry.example.com/rhel-10/rhel-bootc:10.2.
  • --target-imgref: Identifies the image reference that the system uses for future system updates. If this option is not specified, it defaults to the value provided in --source-imgref. Although this option is not mandatory, currently it needs to be specified for the image reference configuration in the installed system. As opposed to the --source-imgref option, it cannot start with a transport prefix (for example, registry.example.com/rhel-10/rhel-bootc:10.2 is a correct format). The bootc tool in the installed system implicitly uses a registry transport.
Note

Do not use this command with the ostreesetup, ostreecontainer, liveimg, %packages, and installation source commands such as cdrom, url, or repo.