So let's have a look at the procedure that you need to go through while using image mode.
First phase is build.
This is where you define your OS deployment using a container file, which creates a custom
image that is based on the boot C container.
Boot C is a specific container image that allows you to boot from the image when it
is deployed to real hardware.
After building the image, you need to deploy.
And that means that you are going to push the image to a registry that target systems
can access.
And then Kickstart can be used to deploy the bare metal as well as virtual machines.
Alternatively, you can use boot C image builder, which is a specific tool that comes with image
mode and that allows you to create formats for specific cloud environments, like QCOW2,
which is used in QEMU, AMI for Amazon, VMDK for vSphere, or DCA for Google.
The next phase is manage.
On systems that are built from boot C containers, the boot C tool can be used to fetch image
updates.
And these updates are provided as container images as well.
It's really the same as when you are updating a regular container to the newer version.
You just fetch a new image and you start running that.
By default, target systems automatically update if a newer version is tagged in a container
registry.
So it will be discovered and it will happen automatically.
A crucial role in image mode is the boot C image.
And the boot C image for RHEL 10 is available through registry.redhat.io.
Obviously it's subject to Red Hat license conditions and for that reason cannot be freely
redistributed.
Also, any derived images cannot be publicly redistributed.
If you need an image that can be freely redistributed, you can use Fedora boot C image instead.
You want more information about it?
Have a look at docs.fedoraproject.org for more information.