Hello everyone,
Please forgive me for asking a beginner question.
I’m having trouble installing MicroOS on a Hyper-V virtual machine.
The VHDX image that launches the interactive installer works as expected. However, I couldn’t install the Cockpit package despite my best efforts. Apparently, this is due to an SELinux issue, and it seems I’m not the only one facing this problem.
That being said, I’m more interested in an automated installation process. I tried using Ignition/Combustion with the same disk image. After encountering some issues while creating a recognized provisioning media as VHDX in Windows, I made some progress using ISO media. However, Ignition isn’t fully taken into account—some parts seem to be ignored.
MicroOS offers an offline image. The main difference between the offline and self-install/raw images are that the offline image has an installer. Raw and self-install allows for customization via combustion or manually in the image after it is written to the disk. There is an option for a real-time kernel.
Honestly, I cannot understand the previous description.
But I’m also considering trying the ContainerHost image, which, from what I understand, is a version more suitable for hosting containers—my ultimate goal.
Unfortunately, this image completely ignores the provisioning ISO media in the VM, boots quickly, and leaves me unable to log in.
Here are my questions:
- What are the differences between the non-ContainerHost and ContainerHost images?
- How can I log in to or provision the ContainerHost image?