Modifying Kernel Arguments

The anaconda bootloader verb can be used to configure kernel arguments. Note that like everything else configured via Anaconda, once set these arguments become "unmanaged" machine-specific state.

The bootc install configuration file supports customizations.kernel.append. See the upstream documentation.

Note that like everything else set via the bootc-image-builder install config, once set these arguments become "unmanaged" machine-specific state.

When using bootc install, it is possible to add install-time kernel arguments both in the container image, and via bootc install --karg. "Day 2 updatable" kernel arguments are supported as well.

Part of the longer term design is that both Anaconda and bootc-image-builder will start internally using bootc install to-filesystem code, and hence also gain support for bootc install configuration. You can follow updates in the following two upstream trackers:

Note that like Anaconda and bootc-image-builder, the bootc install configuration is applied exactly once at install time, and thereafter becomes machine specific state.

The canonical kernel arguments are maintained in /boot/loader/entries. While the /boot filesystem is expected to be mounted read-only by default, it is supported to edit these files directly:

Note that doing so will currently change the existing bootloader entry.

The current base images do include rpm-ostree which has rpm-ostree kargs; however, it is likely that rpm-ostree will be dropped from the default base image.

Kernel arguments can also be shipped when updating the bootc container, for instance, by adding a new .toml config to /usr/lib/bootc/kargs.d/. For details, please refer to the upstream documentation.