3.9. Deploying an image mode for RHEL systems by using FDO

Procedure

1. Create a Containerfile, for example:

   FROM registry.redhat.io/rhel10/rhel-bootc:latest
   RUN dnf install -y fdo-init fdo-client
   RUN systemctl enable fdo-client-linuxapp.service

2. Create your Kickstart file. The following Kickstart file is an example of a fully unattended Kickstart file configuration that contains user creation and partition instructions.

   [customizations.installer.kickstart]
   contents = """
   text --non-interactive
   zerombr
   clearpart --all --initlabel --disklabel=gpt
   autopart --noswap --type=lvm
   user --name=test --groups=wheel --plaintext --password=test
   sshkey --username=test "ssh-ed25519 AAA..."
   network --bootproto=dhcp --device=link --activate --onboot=on
   poweroff
   
   %post
   export MANUFACTURING_SERVER_URL="http://192.168……"
   export DIUN_PUB_KEY_INSECURE="true"
   /usr/libexec/fdo/fdo-manufacturing-client
   %end
   
   """

   In the export <MANUFACTURING_SERVER_URL> field, replace the manufacturing server URL with your own manufacturing server URL.

3. Save the Kickstart configuration in the .toml format to inject the Kickstart content. For example, config.toml.

4. Create the following folder:

   $ mkdir $(pwd)/output"

5. Run bootc-image-builder, and include the Kickstart file configuration that you want to add to the ISO build. The bootc-image-builder automatically adds the ostreecontainer command that installs the container image.

   $ sudo podman run \
       --rm \
       -it \
       --privileged \
       --pull=newer \
       --security-opt label=type:unconfined_t \
       -v /var/lib/containers/storage:/var/lib/containers/storage \
       -v $(pwd)/config.toml:/config.toml \
       -v $(pwd)/output:/output \
       registry.redhat.io/rhel10/bootc-image-builder:latest \
       --type iso \
       --config /config.toml \
     quay.io/<namespace>/<image>:<tag>

   You can find the resulting .iso image in the output folder.