-
Notifications
You must be signed in to change notification settings - Fork 143
Description
There was a recent conversation in the FCOS Matrix room regarding the discoverability of the Installation Customization section in the docs:
When I recently installed CoreOS on a hosted KVM instance (with only a limited webinterface, no direct access to QEMU or libvirt), I wasn't aware of this method and so I just used 'xorriso' to inject the Ignition file into a live ISO I had downloaded:
xorriso -boot_image any keep -dev fedora-coreos-42.20251012.3.0-live-iso.aarch64.iso -map my_custom_ignition_file.ign /config_injected.ign
Then I uploaded the modified ISO to the hosting provider via its webinterface, booted it up, and started the installation on the commandline, pointing it to the injected Ignition file:sudo coreos-installer install /dev/vda --ignition-file /run/media/iso/config_injected.ign
It might actually make sense to pull it out from the bare metal page and give it its own page, possibly in the "System Configuration" section, next to "Producing an Ignition File".
That seems to me how most people would progress, create their Ignition file and then customize an ISO with that file.
But it also fits into the "Provisioning Machines" section.