ostreecontainer

The ostreecontainer Kickstart command is optional. Use this command for OSTree installations from your custom containers.

Important
The ostreecontainer 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.
Usage with bootc-image-builder

When using bootc-image-builder to create bootable ISOs, the tool automatically injects the %ostreecontainer command into the embedded Kickstart file. Note the following:

  • The end-to-end process from image creation to installation is considered a Technology Preview.
  • The support status remains Technology Preview regardless of whether you write the Kickstart file manually or the tool generates it.
Syntax
ostreecontainer [--stateroot STATEROOT] --url URL [--transport TRANSPORT] [--remote REMOTE] [--no-signature-verification]
Options
  • --no-signature-verification: Use this option to disable verification for an ostree remote.
  • --stateroot: Name of the state directory, also known as "osname". Default value is default.
  • --url: Name of the container image for the registry transport. For example, quay.io/exampleos/foo:latest.
  • --transport: The transport, for example, registry or oci. The default value is registry.

    When performing Kickstart installations, the following commands are available together with ostreecontainer:

  • graphical, text, or cmdline
  • clearpart and zerombr
  • autopart
  • part
  • logvol and volgroup
  • reboot and shutdown
  • lang
  • rootpw
  • sshkey
  • bootloader (available only with the --append optional parameter)
  • user - When you specify a group within the user command, the user account can be assigned only to a group that already exists in the container image.

    The following Kickstart commands are unsupported together with ostreecontainer:

  • authconfig and authselect (provide relevant configuration in the container image instead)
  • ostreesetup
  • liveimg
  • module
  • %packages (any necessary packages must be already available in the container image)
  • repo
  • url (if installation requires a stage2 image, such as during PXE installations, use inst.stage2= on the kernel command line. Do not provide a stage2 URL in the Kickstart file.)
  • zfcp
  • zipl

    Kickstart commands not listed here can be used with the ostreecontainer command. However, they are not guaranteed to work as expected in the same way as with package-based installations.

Note
  • The ostreecontainer option cannot be used with the ostreesetup command.