Uploaded image for project: 'RHEL Documentation'
  1. RHEL Documentation
  2. RHELDOCS-20362

Issues With RHEL Image Mode Guide

XMLWordPrintable

    • None
    • rhel-sst-ccs
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • CCS 2025-15, CCS 2025-16, CCS 2025-17, CCS 2025-18
    • None
    • Unspecified
    • Unspecified
    • Unspecified

      As a follow-up to https://issues.redhat.com/browse/RHELDOCS-20235, I now see the following, these apply probably to the corresponding RHEL 9 guide as well.

      0) In section 4.1 in https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/using_image_mode_for_rhel_to_build_deploy_and_manage_operating_systems/creating-bootc-compatible-base-disk-images-with-bootc-image-builder there is a note about private registries not supported, perhaps could clarify why is this and is this expected to change, if this is still valid?

      1) Examples in section 4.3 in https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/using_image_mode_for_rhel_to_build_deploy_and_manage_operating_systems/creating-bootc-compatible-base-disk-images-with-bootc-image-builder#creating-qcow2-images-by-using-bootc-image-builder are needlessly inconsistent with paths, either use . (preferable) or $(pwd) in both, not mix them needlessly. And why only one of config mappings is marked with ":ro"? Also, the former example seems to be lacking --config altogether? NB, the --local line is missing a backslash at the end thus copy-paste will fail and --local is explained only in the VMDK section not in the Qcow2 section which is the first one. There's also a warning --local being the default and suggestion to remove it when running the command / latest image so perhaps just remove it? Using --pull seems not essential here after a pull in the previous section? Finally, strictly speaking -t is enough, -it not needed since the tool is not interactive.

      It should be explained what a public and private Qcow2 images are in this case, if they are placed in the local output folder? Since the first example doesn't even start it's hard to know this.

      I think all 4.x section should be reviewed and tested for these issues to ensure the examples are indeed correct and working.

      2) In section 6 intro in https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/using_image_mode_for_rhel_to_build_deploy_and_manage_operating_systems/deploying-the-rhel-bootc-images bootc-install is not described unlike bootc-image-builder before a diagram using it as part of a worfklow is shown.

      3) In section 6.1 the link to Creating QCOW2 images by using bootc-image-builder does not work.

      4) In section 6.1 virt-install is used to import a Qcow2 image but the intro suggest a container image (which one?) should be available in a container repo after building the Qcow2, why would that be needed at this stage since the reference can be changed? It feels the requirements are copy-pasted since the required disk image is not included in them? Also, always using "Qcow2 image" instead of "QEMU disk image" at least once would be more consistent and also more correct since non-QEMU platforms like AHV use Qcow2 and the text mentions "a virtualization software."

      Thanks.

              elpereir@redhat.com Eliane Pereira
              myllynen Marko Myllynen
              RHEL Docs RHEL Docs
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: