Requirements for specific target platforms

Review the specific requirements and procedures necessary to prepare operating system images for deployment onto target platforms such as Red Hat OpenShift Virtualization and VMware vSphere.

Build images for Red Hat OpenShift Virtualization
Copy link

When building operating system images and disk images for Red Hat OpenShift Virtualization, you can follow the generic image building process with the following changes:

About this task
Copy link

  • Using late binding by injecting the enrollment certificate or the agent configuration through cloud-init when provisioning the virtual device.
  • Adding the open-vm-tools guest tools to the image.
  • Building a disk image of type qcow2 instead of iso.

Complete the generic steps with changes to the following steps:

Procedure
Copy link

  1. Build an operating system image based on RHEL 9 that includes the Red Hat Edge Manager agent and VM guest tools but excludes the agent configuration.
  2. Create a file named Containerfile with the following content: 
    FROM registry.redhat.io/rhel9/bootc-image-builder:latest
RUN subscription-manager repos --enable ansible-automation-platform-2.5-for-rhel-9-x86_64-rpms
    dnf -y install flightctl-agent && \
    dnf -y clean all && \
    systemctl enable flightctl-agent.service
RUN dnf -y install cloud-init open-vm-tools && \
    dnf -y clean all && \
    ln -s ../cloud-init.target /usr/lib/systemd/system/default.target.wants && \
    systemctl enable vmtoolsd.service
  3. Optional: To enable podman-compose application support, add the following section to the Containerfile file: 
    RUN dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm && \
    dnf -y install podman-compose && \
    dnf -y clean all && \
    systemctl enable podman.service

Build the bootc image
Copy link

Build, sign, and publish the bootc operating system image by following the generic image building process:

About this task
Copy link

Procedure
Copy link

  1. Create a directory called output by running the following command: 
    mkdir -p output
  2. Generate an operating system disk image of type vmdk from your operating system image by running the following command: 
    sudo podman run --rm -it --privileged --pull=newer \
    --security-opt label=type:unconfined_t \
    -v "${PWD}/output":/output \
    -v /var/lib/containers/storage:/var/lib/containers/storage \
    registry.redhat.io/rhel9/bootc-image-builder:latest \
    --type qcow2 \
    ${OCI_IMAGE_REPO}:${OCI_IMAGE_TAG}

What to do next
Copy link

When the bootc-image-builder completes, you can find the disk image under ${PWD}/output/vmdk/disk.vmdk.

Build the QCoW2 disk image
Copy link

Red Hat OpenShift Virtualization can download disk images from an OCI registry but it expects a container disk image instead of an OCI artifact.

About this task
Copy link

Complete the following steps to build, sign, and upload the QCoW2 disk image:

Procedure
Copy link

  1. Create a file called Containerfile.qcow2 with the following content: 
    FROM registry.access.redhat.com/ubi9/ubi:latest AS builder
ADD --chown=107:107 output/qcow2/disk.qcow2 /disk/
RUN chmod 0440 /disk/*
FROM scratch
COPY --from=builder /disk/* /disk/
    ADD --chown=107:107 output/qcow2/disk.qcow2 /disk/
    Adds the QCoW2 disk image to a builder container to set the required 107 file ownership, which is the QEMU user.
    RUN chmod 0440 /disk/*
    Sets the required 0440 file permissions.
    COPY --from=builder /disk/* /disk/
    Copies the file to a scratch image.
  2. Build, sign, and publish your disk image by running the following command: 
    sudo chown -R $(whoami):$(whoami) "${PWD}/output"
OCI_DISK_IMAGE_REPO=${OCI_IMAGE_REPO}/diskimage-qcow2
sudo podman build -t ${OCI_DISK_IMAGE_REPO}:${OCI_IMAGE_TAG} -f Containerfile.qcow2 .
sudo podman push --sign-by-sigstore-private-key ./signingkey.private ${OCI_DISK_IMAGE_REPO}:${OCI_IMAGE_TAG}

Build images for VMware vSphere
Copy link

When building operating system images and disk images for VMware vSphere, you can follow the generic image building process with the following changes:

About this task
Copy link

  • Using late binding by injecting the enrollment certificate or the agent configuration through cloud-init when provisioning the virtual device.
  • Adding the open-vm-tools guest tools to the image.
  • Building a disk image of type vmdk instead of iso.

Complete the generic steps with changes to the following steps:

Procedure
Copy link

  1. Build an operating system image based on RHEL 9 that includes the Red Hat Edge Manager agent and VM guest tools but excludes the agent configuration.
  2. Create a file named Containerfile with the following content: 
    FROM registry.redhat.io/rhel9/bootc-image-builder:latest
RUN subscription-manager repos --enable ansible-automation-platform-2.5-for-rhel-9-x86_64-rpms
    dnf -y install flightctl-agent && \
    dnf -y clean all && \
    systemctl enable flightctl-agent.service && \
RUN dnf -y install cloud-init open-vm-tools && \
    dnf -y clean all && \
    ln -s ../cloud-init.target /usr/lib/systemd/system/default.target.wants && \
    systemctl enable vmtoolsd.service
  3. Create a directory called output by running the following command: 
    mkdir -p output
  4. Generate an operating system disk image of type vmdk from your operating system image by running the following command: 
    sudo podman run --rm -it --privileged --pull=newer \
    --security-opt label=type:unconfined_t \
    -v "${PWD}/output":/output \
    -v /var/lib/containers/storage:/var/lib/containers/storage \
    registry.redhat.io/rhel9/bootc-image-builder:latest \
    --type vmdk \
    ${OCI_IMAGE_REPO}:${OCI_IMAGE_TAG}

What to do next
Copy link

When the bootc-image-builder completes, you can find the disk image under ${PWD}/output/vmdk/disk.vmdk.