Between the chapter https://docs.redhat.com/en/documentation/red_hat_build_of_microshift/4.17/html/installing_with_rhel_image_mode/installing-with-rhel-image-mode#microshift-rhel-image-mode-run-container_microshift-install-rhel-image-mode and https://docs.redhat.com/en/documentation/red_hat_build_of_microshift/4.17/html/installing_with_rhel_image_mode/installing-with-rhel-image-mode#accessing-microshift-cluster-remotely_microshift-install-rhel-image-mode the docs assume that MicroShift has been installed on a "real" host.
This implies the conversion of the container to a hardware/VM format and its instantiation, both covering certain challenges not covered in the docs, at least:
1. have /etc/crio/openshift-pull-secret pushed inside the image (it's only mapped into the container).
2. probably make sure that LVM is used to give storage to µShift, with a VG with disk space left...
I assume that it's possible with the right blueprint, but getting the basis would help.

    n/a

    n/a

    1. read :-)

See above    

I'd expect one additional chapter explaining for ISO and at least one image format (qcow2, raw, vmdk, etc) how to guarantee the basic features as described above to make MicroShift run successfully on VM/hardware.