Composing, installing, and managing RHEL for Edge images

1. Composing a RHEL rpm-ostree image using the RHEL image builder tool. You can access RHEL image builder on the command line by using the composer-cli tool, or use a graphical user interface in the RHEL web console.
2. Deploying the image by using RHEL installer.

1. Install and register a RHEL system
2. Install RHEL image builder
3. Using RHEL image builder, create a blueprint with customizations for RHEL for Edge Container image
4. Import the RHEL for Edge blueprint in RHEL image builder
5. Create a RHEL for Edge image embed in an OCI container with a webserver ready to deploy the commit as an OSTree repository
6. Download the RHEL for Edge Container image file
7. Deploy the container serving a repository with the RHEL for Edge Container commit
8. Using RHEL image builder, create another blueprint for RHEL for Edge Installer image
9. Create a RHEL for Edge Installer image configured to pull the commit from the running container embedded with RHEL for Edge Container image
10. Download the RHEL for Edge Installer image
11. Run the installation

1. Install and register a RHEL system
2. Install RHEL image builder
3. Using RHEL image builder, create a blueprint for RHEL for Edge image
4. Import the RHEL for Edge blueprint in RHEL image builder
5. Create a RHEL for Edge Commit (.tar) image
6. Download the RHEL for Edge image file
7. On the same system where you have installed RHEL image builder, install a web server that you want to serve the RHEL for Edge Commit content. For instructions, see Setting up and configuring NGINX
8. Extract the RHEL for Edge Commit (.tar) content to the running web server
9. Create a Kickstart file that pulls the OSTree content from the running web server. For details on how to modify the Kickstart to pull the OSTree content, see Extracting the RHEL for Edge image commit
10. Boot the RHEL installer ISO on the edge device and provide the Kickstart to it.

Procedure

1. Install the following packages on the virtual machine.

   • osbuild-composer
   • composer-cli
   • cockpit-composer
   • bash-completion
   • firewalld

   # dnf install osbuild-composer composer-cli cockpit-composer bash-completion firewalld

   Copy to Clipboard Toggle word wrap

   RHEL image builder is installed as an application in RHEL web console.

2. Reboot the virtual machine

3. Configure the system firewall to allow access to the web console:

   # firewall-cmd --add-service=cockpit && firewall-cmd --add-service=cockpit --permanent

   Copy to Clipboard Toggle word wrap

4. Enable RHEL image builder.

   # systemctl enable osbuild-composer.socket cockpit.socket --now

   Copy to Clipboard Toggle word wrap

   The osbuild-composer and cockpit services start automatically on first access.

5. Load the shell configuration script so that the autocomplete feature for the composer-cli command starts working immediately without reboot:

   $ source /etc/bash_completion.d/composer-cli

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a repository source file, such as /root/repo.toml. For example:

   id = "k8s"
   name = "Kubernetes"
   type = "yum-baseurl"
   url = "https://server.example.com/repos/company_internal_packages/"
   check_gpg = false
   check_ssl = false
   system = false

   Copy to Clipboard Toggle word wrap

   The type field accepts the following valid values: yum-baseurl, yum-mirrorlist, and yum-metalink.

2. Save the file in the TOML format.

3. Add the new third-party source to RHEL image builder:

   $ composer-cli sources add <file-name>.toml

   Copy to Clipboard Toggle word wrap

Verification

1. Check if the new source was successfully added:

   $ composer-cli sources list

   Copy to Clipboard Toggle word wrap

2. Check the new source content:

   $ composer-cli sources info <source_id>

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a repository source file, such as /root/repo.toml. For example, to specify the distribution:

   check_gpg = true
   check_ssl = true
   distros = ["rhel-9"]
   id = "rh9-local"
   name = "packages for RHEL"
   system = false
   type = "yum-baseurl"
   url = "https://local/repos/rhel9/projectrepo/"

   Copy to Clipboard Toggle word wrap
2. Save the file in the TOML format.

3. Add the new third-party source to RHEL image builder:

   $ composer-cli sources add <file-name>.toml

   Copy to Clipboard Toggle word wrap

Verification

1. Check if the new source was successfully added:

   $ composer-cli sources list

   Copy to Clipboard Toggle word wrap

2. Check the new source content:

   $ composer-cli sources info <source_id>

   Copy to Clipboard Toggle word wrap

Procedure

1. Access the folder where you want to create a repository:

   $ cd repo/

   Copy to Clipboard Toggle word wrap

2. Run the createrepo_c to create a repository from RPM packages:

   $ createrepo_c .

   Copy to Clipboard Toggle word wrap

3. Access the directory where the repodata is:

   $ cd repodata/

   Copy to Clipboard Toggle word wrap

4. Sign your repomd.xml file:

   $ gpg -u <_gpg-key-email_> --yes --detach-sign --armor /srv/repo/example/repomd.xml

   Copy to Clipboard Toggle word wrap

5. To enable GPG signature checks in the repository:

   1. Set check_repogpg = true in the repository source.

   2. Enter the gpgkey that you want to do the check. If your key is available over https, set the gpgkeys field with the key URL for the key. You can add as many URL keys as you need.

      The following is an example:

      check_gpg = true
      check_ssl = true
      id = "signed local packages"
      name = "repository_name"
      type = "yum-baseurl"
      url = "https://local/repos/projectrepo/"
      check_repogpg = true
      gpgkeys=["https://local/keys/repokey.pub"]

      Copy to Clipboard Toggle word wrap

      As an alternative, add the GPG key directly in the gpgkeys field, for example:

      check_gpg = true
      check_ssl = true
      check_repogpg
      id = "custom-local"
      name = "signed local packages"
      type = "yum-baseurl"
      url = "https://local/repos/projectrepo/"
      gpgkeys=["https://remote/keys/other-repokey.pub",
      '''-----BEGIN PGP PUBLIC KEY BLOCK-----
      …​
      -----END PGP PUBLIC KEY BLOCK-----''']

      Copy to Clipboard Toggle word wrap

      • If the test does not find the signature, the GPG tool shows an error similar to the following one:

        $ GPG verification is enabled, but GPG signature is not available.
        This may be an error or the repository does not support GPG verification:
        Status code: 404 for http://repo-server/rhel/repodata/repomd.xml.asc (IP: 192.168.1.3)

        Copy to Clipboard Toggle word wrap

      • If the signature is invalid, the GPG tool shows an error similar to the following one:

        repomd.xml GPG signature verification error: Bad GPG signature

        Copy to Clipboard Toggle word wrap

Procedure

1. Create the /etc/osbuild-composer/repositories/ directory to store your repository overrides:

   $ sudo mkdir -p /etc/osbuild-composer/repositories

   Copy to Clipboard Toggle word wrap

2. Create a JSON file, using a name corresponding to your RHEL version. Alternatively, you can copy the file for your distribution from /usr/share/osbuild-composer/ and modify its content.

   For RHEL 9.3, use /etc/osbuild-composer/repositories/rhel-93.json.

3. Add the following structure to your JSON file. Specify only one of the following attributes, in the string format:

   • baseurl - The base URL of the repository.
   • metalink - The URL of a metalink file that contains a list of valid mirror repositories.

   • mirrorlist - The URL of a mirrorlist file that contains a list of valid mirror repositories. The remaining fields, such as gpgkey, and metadata_expire, are optional.

     For example:

     {
          "x86_64": [
             {
                 "name": "baseos",
                 "baseurl": "http://mirror.example.com/composes/released/RHEL-9/9.0/BaseOS/x86_64/os/",
                 "gpgkey": "-----BEGIN PGP PUBLIC KEY BLOCK-----\n\n (…​)",
                 "check_gpg": true
             }
         ]
     }

     Copy to Clipboard Toggle word wrap

     Alternatively, you can copy the JSON file for your distribution, by replacing rhel-version.json with your RHEL version, for example: rhel-9.json.

     $  cp /usr/share/osbuild-composer/repositories/rhel-version.json /etc/osbuild-composer/repositories/

     Copy to Clipboard Toggle word wrap

4. Optional: Verify the JSON file:

   $ json_verify < /etc/osbuild-composer/repositories/rhel-version.json

   Copy to Clipboard Toggle word wrap

5. Edit the baseurl paths in the rhel-9.json file and save it. For example:

   $ /etc/osbuild-composer/repositories/rhel-version.json

   Copy to Clipboard Toggle word wrap

6. Restart the osbuild-composer.service:

   $ sudo systemctl restart osbuild-composer.service

   Copy to Clipboard Toggle word wrap

Procedure

1. Get the baseurl from the /etc/yum.repos.d/redhat.repo file:

   # cat /etc/yum.repos.d/redhat.repo
   [AppStream]
   name = AppStream mirror example
   baseurl = https://mirror.example.com/RHEL-9/9.0/AppStream/x86_64/os/
   enabled = 1
   gpgcheck = 0
   sslverify = 1
   sslcacert = /etc/pki/ca1/ca.crt
   sslclientkey = /etc/pki/ca1/client.key
   sslclientcert = /etc/pki/ca1/client.crt
   metadata_expire = 86400
   enabled_metadata = 0

   Copy to Clipboard Toggle word wrap

2. Configure the repository override to use the same baseurl and set rhsm to true:

   {
       "x86_64": [
           {
               "name": "AppStream mirror example",
               "baseurl": "https://mirror.example.com/RHEL-9/9.0/AppStream/x86_64/os/",
               "gpgkey": "-----BEGIN PGP PUBLIC KEY BLOCK-----\n\n (…​)",
               "check_gpg": true,
               "rhsm": true
           }
       ]
   }

   Copy to Clipboard Toggle word wrap

3. Restart the osbuild-composer.service:

   $ sudo systemctl restart osbuild-composer.service

   Copy to Clipboard Toggle word wrap

Procedure

1. Find the repository URL from your currently configured repositories:

   $ sudo yum -v repolist "-baseos-rpms" | grep -i repo-baseurl
     Repo-baseurl :

   Copy to Clipboard Toggle word wrap

   The following output is an example:

   https://satellite6.example.com/pulp/content/YourOrg/YourEnv/YourCV/content/dist/rhel9/9/x86_64/baseos/os

   Copy to Clipboard Toggle word wrap

2. Modify the hard-coded repositories to a Satellite Server.

   1. Create a repository directory with the 0755 permission:

      $ sudo mkdir -pvm 0755 /etc/osbuild-composer/repositories

      Copy to Clipboard Toggle word wrap

   2. Copy the content from /usr/share/osbuild-composer/repositories/*.json to the directory that you created:

      $ sudo cp /usr/share/osbuild-composer/repositories/*.json /etc/osbuild-composer/repositories/

      Copy to Clipboard Toggle word wrap

   3. Update the Satellite URL and the file contents through the /content/dist/* line:

      $ sudo sed -i -e 's|cdn.redhat.com|satellite6.example.com/pulp/content/YourOrg/YourEnv/YourCV|' /etc/osbuild-composer/repositories/*.json

      Copy to Clipboard Toggle word wrap

   4. Verify that the configuration was correctly replaced:

      $ sudo vi /etc/osbuild-composer/repositories/rhel-9.json

      Copy to Clipboard Toggle word wrap

3. Restart the services:

   $ sudo systemctl restart osbuild-worker@1.service osbuild-composer.service

   Copy to Clipboard Toggle word wrap
4. Override the required system repository in Red Hat image builder configuration and use the URL of your Satellite repository as a baseurl. See Overriding a system repository.

Procedure

1. In the Satellite web UI, navigate to Content > Products, select your Product and click the repository you want to use.
2. Search for the secured URL (HTTPS) in the Published field and copy it.
3. Use the URL that you copied as a baseurl for the Red Hat image builder repository. See Adding custom third-party repositories to RHEL image builder.

Procedure

1. On your RHEL system, access https://localhost:9090/ in a web browser.
2. For more information about how to remotely access RHEL image builder, see Managing systems using the RHEL 9 web console document.
3. Log in to the web console using an administrative user account.
4. On the web console, in the left hand menu, click Apps.

5. Click Image Builder.

   The RHEL image builder dashboard opens in the right pane. You can now proceed to create a blueprint for the RHEL for Edge images.

Procedure

1. On the RHEL image builder dashboard, click Create Blueprint.

   The Create Blueprint dialogue box opens.

2. On the Details page:

   1. Enter the name of the blueprint and, optionally, its description. Click Next.

3. Optional: In the Packages page:

   1. On the Available packages search, enter the package name and click the > button to move it to the Chosen packages field. Search and include as many packages as you want. Click Next.

      Note

      These customizations are all optional unless otherwise specified.

4. On the Kernel page, enter a kernel name and the command-line arguments.
5. On the File system page, select Use automatic partitioning. OSTree systems do not support filesystem customization, because OSTree images have their own mount rule, such as read-only. Click Next.

6. On the Services page, you can enable or disable services:

   1. Enter the service names you want to enable or disable, separating them by a comma, by space, or by pressing the Enter key. Click Next.

7. On the Firewall page, set up your firewall setting:

   1. Enter the Ports, and the firewall services you want to enable or disable.
   2. Click the Add zone button to manage your firewall rules for each zone independently. Click Next.

8. On the Users page, add a users by following the steps:

   1. Click Add user.
   2. Enter a Username, a password, and a SSH key. You can also mark the user as a privileged user, by clicking the Server administrator checkbox. Click Next.

9. On the Groups page, add groups by completing the following steps:

   1. Click the Add groups button:

      1. Enter a Group name and a Group ID. You can add more groups. Click Next.

10. On the SSH keys page, add a key:

    1. Click the Add key button.

       1. Enter the SSH key.
       2. Enter a User. Click Next.

11. On the Timezone page, set your timezone settings:

    1. On the Timezone field, enter the timezone you want to add to your system image. For example, add the following timezone format: "US/Eastern".

       If you do not set a timezone, the system uses Universal Time, Coordinated (UTC) as default.

    2. Enter the NTP servers. Click Next.

12. On the Locale page, complete the following steps:

    1. On the Keyboard search field, enter the package name you want to add to your system image. For example: ["en_US.UTF-8"].
    2. On the Languages search field, enter the package name you want to add to your system image. For example: "us". Click Next.

13. On the Others page, complete the following steps:

    1. On the Hostname field, enter the hostname you want to add to your system image. If you do not add a hostname, the operating system determines the hostname.
    2. Mandatory only for the Simplifier Installer image: On the Installation Devices field, enter a valid node for your system image. For example: dev/sda. Click Next.

14. Mandatory only when building FIDO images: On the FIDO device onboarding page, complete the following steps:

    1. On the Manufacturing server URL field, enter the following information:

       1. On the DIUN public key insecure field, enter the insecure public key.
       2. On the DIUN public key hash field, enter the public key hash.
       3. On the DIUN public key root certs field, enter the public key root certs. Click Next.

15. On the OpenSCAP page, complete the following steps:

    1. On the Datastream field, enter the datastream remediation instructions you want to add to your system image.
    2. On the Profile ID field, enter the profile_id security profile you want to add to your system image. Click Next.

16. Mandatory only when building Ignition images: On the Ignition page, complete the following steps:

    1. On the Firstboot URL field, enter the package name you want to add to your system image.
    2. On the Embedded Data field, drag or upload your file. Click Next.
17. . On the Review page, review the details about the blueprint. Click Create.

1. From the More Options menu, click Download.

   The RHEL image builder tool downloads the file at your default download location.

Procedure

1. Extract the downloaded image .tar file:

   # tar xvf <UUID>-commit.tar

   Copy to Clipboard Toggle word wrap

2. Go to the directory where you have extracted the .tar file.

   It has a compose.json file and an OSTree directory. The compose.json file has the commit number and the OSTree directory has the RPM packages.

3. Open the compose.json file and note the commit ID number. You need this number handy when you proceed to set up a web server.

   If you have the jq JSON processor installed, you can also retrieve the commit ID by using the jq tool:

   # jq '.["ostree-commit"]' < compose.json

   Copy to Clipboard Toggle word wrap

4. List the RPM packages in the commit.

   # rpm-ostree db list rhel/9/x86_64/edge --repo=repo

   Copy to Clipboard Toggle word wrap

5. Use a Kickstart file to run the RHEL installer. Optionally, you can use any existing file or can create one by using the Kickstart Generator tool.

   In the Kickstart file, ensure that you include the details about how to provision the file system, create a user, and how to fetch and deploy the RHEL for Edge image. The RHEL installer uses this information during the installation process.

   The following is a Kickstart file example:

   lang en_US.UTF-8
   keyboard us
   timezone Etc/UTC --isUtc
   text
   zerombr
   clearpart --all --initlabel
   autopart
   reboot
   user --name=core --group=wheel
   sshkey --username=core "ssh-rsa AAAA3Nza…​."
   rootpw --lock
   network --bootproto=dhcp
   
   ostreesetup --nogpg --osname=rhel --remote=edge --url=https://mirror.example.com/repo/ --ref=rhel/9/x86_64/edge

   Copy to Clipboard Toggle word wrap

   The OStree-based installation uses the ostreesetup command to set up the configuration. It fetches the OSTree commit, by using the following flags:

   • --nogpg - Disable GNU Privacy Guard (GPG) key verification.
   • --osname - Management root for the operating system installation.
   • --remote - Management root for the operating system installation
   • --url - URL of the repository to install from.
   • --ref - Name of the branch from the repository that the installation uses.

   • --url=http://mirror.example.com/repo/ - is the address of the host system where you extracted the edge commit and served it over nginx. You can use the address to reach the host system from the guest computer.

     For example, if you extract the commit image in the /var/www/html directory and serve the commit over nginx on a computer whose hostname is www.example.com, the value of the --url parameter is http://www.example.com/repo.

     Note

     Use the http protocol to start a service to serve the commit, because https is not enabled on the Apache HTTP Server.

Procedure

1. Install the HTTPd server package:

   $ dnf install httpd

   Copy to Clipboard Toggle word wrap

2. Copy the extracted RHEL for Edge image content to the web server document root:

   # cp kickstart.ks /var/www/html/
   # cp -r repo /var/www/html/
   # cp <uuid_commit>.tar /var/www/html/

   Copy to Clipboard Toggle word wrap

3. Start and enable the HTTPd service:

   # systemctl enable --now httpd
   # systemctl status httpd.service

   Copy to Clipboard Toggle word wrap

4. Configure the firewall to enable HTTP traffic:

   # firewall-cmd --permanent --add-service=http
   # firewall-cmd --reload

   Copy to Clipboard Toggle word wrap

   The server is now set up and ready to start the RHEL Installer by using the commit.tar repository and the Kickstart file.

   The files are accessible at the following locations:

Procedure

1. Create a Kickstart file. The following is an example in which the ostreesetup directive instructs the Anaconda Installer to fetch and deploy the commit. Additionally, it creates a user and a password.

   lang en_US.UTF-8
   keyboard us
   timezone UTC
   zerombr
   clearpart --all --initlabel
   autopart --type=plain --fstype=xfs --nohome
   reboot
   text
   network --bootproto=dhcp
   user --name=core --groups=wheel --password=edge
   services --enabled=ostree-remount
   ostreesetup --nogpg --url=http://edge_device_ip:port/repo/ --osname=rhel --remote=edge --ref=rhel/9/x86_64/edge

   Copy to Clipboard Toggle word wrap

2. Run the RHEL Anaconda Installer by using the libvirt virt-install utility to create a virtual machine (VM) with a RHEL operating system. Use the .qcow2 disk image as the target disk in the attended installation:

   virt-install \
   --name rhel-edge-test-1 \
   --memory 2048 \
   --vcpus 2 \
   --disk path=prepared_disk_image.qcow2,format=qcow2,size=8 \
   --os-variant rhel9 \
   --cdrom /home/username/Downloads/rhel-9-x86_64-boot.iso

   Copy to Clipboard Toggle word wrap

3. On the installation screen:

   Figure 6.1. Red Hat Enterprise Linux boot menu

   

   View larger image

   

   1. Press the e key to add an additional kernel parameter:

      inst.ks=http://web-server_device_ip:port/kickstart.ks

      Copy to Clipboard Toggle word wrap

      The kernel parameter specifies that you want to install RHEL by using the Kickstart file and not the RHEL image contained in the RHEL Installer.

   2. After adding the kernel parameters, press Ctrl+X to boot the RHEL installation by using the Kickstart file.

      The RHEL Installer starts, fetches the Kickstart file from the server (HTTP) endpoint and executes the commands, including the command to install the RHEL for Edge image commit from the HTTP endpoint. After the installation completes, the RHEL Installer prompts you for login details.

Verification

1. On the Login screen, enter your user account credentials and click Enter.

2. Verify whether the RHEL for Edge image is successfully installed.

   $ rpm-ostree status

   Copy to Clipboard Toggle word wrap

   The command output provides the image commit ID and shows that the installation is successful.

   Following is a sample output:

   State: idle
   Deployments:
   * ostree://edge:rhel/9/x86_64/edge
   		  Timestamp: 2020-09-18T20:06:54Z
   			Commit: 836e637095554e0b634a0a48ea05c75280519dd6576a392635e6fa7d4d5e96

   Copy to Clipboard Toggle word wrap

Procedure

1. Run a RHEL for Edge Container image to start a web server. The server fetches the commit in the RHEL for Edge Container image and becomes available and running.

2. Run the RHEL Anaconda Installer, passing the customized .qcow2 disk image, by using libvirt virt-install:

   virt-install \
   --name rhel-edge-test-1 \
   --memory 2048 \
   --vcpus 2 \
   --disk path=prepared_disk_image.qcow2,format=qcow2,size=8 \
   --os-variant rhel9 \
   --cdrom /home/username/Downloads/rhel-9-x86_64-boot.iso

   Copy to Clipboard Toggle word wrap

3. On the installation screen:

   Figure 6.2. Red Hat Enterprise Linux boot menu

   

   View larger image

   

   1. Press the TAB key and add the Kickstart kernel argument:

      inst.ks=http://web-server_device_ip:port/kickstart.ks

      Copy to Clipboard Toggle word wrap

      The kernel parameter specifies that you want to install RHEL by using the Kickstart file and not the RHEL image contained in the RHEL Installer.

   2. After adding the kernel parameters, press Ctrl+X to boot the RHEL installation by using the Kickstart file.

      The RHEL Installer starts, fetches the Kickstart file from the server (HTTP) endpoint, and executes the commands, including the command to install the RHEL for Edge image commit from the HTTP endpoint. After the installation completes, the RHEL Installer prompts you for login details.

Verification

1. On the Login screen, enter your user account credentials and click Enter.

2. Verify whether the RHEL for Edge image is successfully installed.

   $ rpm-ostree status

   Copy to Clipboard Toggle word wrap

   The command output provides the image commit ID and shows that the installation is successful.

   The following is a sample output:

   State: idle
   Deployments:
   * ostree://edge:rhel/9/x86_64/edge
   		  Timestamp: 2020-09-18T20:06:54Z
   			Commit: 836e637095554e0b634a0a48ea05c75280519dd6576a392635e6fa7d4d5e96

   Copy to Clipboard Toggle word wrap

Procedure

1. Navigate to the directory where you have downloaded the RHEL for Edge Container OSTree commit.

2. Load the RHEL for Edge Container OSTree commit into Podman.

   $ sudo podman load -i UUID-container.tar

   Copy to Clipboard Toggle word wrap

   The command output provides the image ID, for example: @8e0d51f061ff1a51d157804362bc875b649b27f2ae1e66566a15e7e6530cec63

3. Tag the new RHEL for Edge Container image, using the image ID generated by the previous step.

   $ sudo podman tag image-ID localhost/edge-container

   Copy to Clipboard Toggle word wrap

   The podman tag command assigns an additional name to the local image.

4. Run the container named edge-container.

   $ sudo podman run -d --name=edge-container -p 8080:8080 localhost/edge-container

   Copy to Clipboard Toggle word wrap

   The podman run -d --name=edge-container command assigns a name to your container-based on the localhost/edge-container image.

5. List containers:

   $ sudo podman ps -a
   CONTAINER ID  IMAGE                               	COMMAND	CREATED    	STATUS                	PORTS   NAMES
   2988198c4c4b  …./localhost/edge-container   /bin/bash  3 seconds ago  Up 2 seconds ago      	edge-container

   Copy to Clipboard Toggle word wrap

Procedure

1. Begin to create the RHEL for Edge Installer image.

   # composer-cli compose start-ostree --ref rhel/9/x86_64/edge --url URL-OSTree-repository blueprint-name image-type

   Copy to Clipboard Toggle word wrap

   Where,

   • ref is the same value that customer used to build OSTree repository
   • URL-OSTree-repository is the URL to the OSTree repository of the commit to embed in the image. For example, http://10.0.2.2:8080/repo/. See Creating a RHEL for Edge Container image for non-network-based deployments.
   • blueprint-name is the RHEL for Edge Installer blueprint name.

   • image-type is edge-installer.

     A confirmation that the composer process has been added to the queue appears. It also shows a Universally Unique Identifier (UUID) number for the image created. Use the UUID number to track your build. Also keep the UUID number handy for further tasks.

2. Check the image compose status.

   # composer-cli compose status

   Copy to Clipboard Toggle word wrap

   The command output displays the status in the following format:

   <UUID> RUNNING date blueprint-name blueprint-version image-type

   Copy to Clipboard Toggle word wrap
   Note

   The image creation process takes a few minutes to complete.

   To interrupt the image creation process, run:

   # composer-cli compose cancel <UUID>

   Copy to Clipboard Toggle word wrap

   To delete an existing image, run:

   # composer-cli compose delete <UUID>

   Copy to Clipboard Toggle word wrap

   RHEL image builder pulls the commit that is being served by the running container during the image build.

   After the image build is complete, you can download the resulting ISO image.

3. Download the image. See Downloading a RHEL for Edge image.

   After the image is ready, you can use it for non-network deployments. See Installing the RHEL for Edge image for non-network-based deployments.

Procedure

1. Create a qcow VM disk file to install the (.iso) image. That is an image of a hard disk drive for the virtual machine (VM). For example:

   $ qemu-img create -f qcow2 diskfile.qcow2 20G

   Copy to Clipboard Toggle word wrap

2. Use the virt-install command to boot the VM using the disk as a drive and the installer ISO image as a CD-ROM. For example:

   $ virt-install \
   --boot uefi \
   --name VM_NAME
   --memory 2048 \
   --vcpus 2 \
   --disk path=diskfile.qcow2
   --cdrom /var/lib/libvirt/images/UUID-installer.iso \
   --os-variant rhel9.0

   Copy to Clipboard Toggle word wrap

   This command instructs virt-install to:

   • Instructs the VM to use UEFI to boot, instead of the BIOS.
   • Mount the installation ISO.

   • Use the hard disk drive image created in the first step.

     It gives you an Anaconda Installer. The RHEL Installer starts, loads the Kickstart file from the ISO and executes the commands, including the command to install the RHEL for Edge image commit. Once the installation is complete, the RHEL installer prompts for login details.

     Note

     Anaconda is preconfigured to use the Container commit during the installation. However, you need to set up system configurations, such as disk partition, timezone, between others.

3. Connect to Anaconda GUI with virt-viewer to setup the system configuration:

   $ virt-viewer --connect qemu:///system --wait VM_NAME

   Copy to Clipboard Toggle word wrap
4. Reboot the system to finish the installation.
5. On the login screen, specify your user account credentials and click Enter.

Verification

1. Verify whether the RHEL for Edge image is successfully installed.

   $  rpm-ostree status

   Copy to Clipboard Toggle word wrap

1. Install and register a RHEL system
2. Install RHEL image builder
3. Using RHEL image builder, create a blueprint with customizations for RHEL for Edge Container image
4. Import the RHEL for Edge blueprint in RHEL image builder
5. Create a RHEL for Edge image embed in an OCI container with a web server ready to deploy the commit as an OSTree repository
6. Create a blueprint for the edge-simplified-installer image
7. Build a simplified RHEL for Edge image
8. Download the RHEL for Edge simplified image
9. Install the raw image with the edge-simplified-installer virt-install