cat src/config/live/README-devel.md
These files will be copied to the target live ISO
via the CoreOS Assembler buildextend-live call. It
picks up all files in the coreos/fedora-coreos-config/live/
directory and copies them to the base of the ISO.
Files currently copied are:
isolinux/boot.msg
isolinux/isolinux.cfg
Files that get copied into efiboot.img in the ISO:
EFI/grub.cfg
so i tried to be smart and embed a core.ign into it by adding the core.ign to the live directory
i can see where cosa picked it up, yet i dont see anything on the live filesystem
The files in fedora-coreos-config/live are copied to the root of the ISO filesystem, not the root of the live filesystem. The live ISO is fairly intricate; I’d suggest reading through cmd-buildextend-live if you’d like to see how all the pieces fit together.
coreos-installer iso ignition embed -f ignition-files/ignition.ign -o new-image.iso fedora-coreos-36.20220529.dev.0-live.x86_64.iso
error: Found argument ‘fedora-coreos-36.20220529.dev.0-live.x86_64.iso’ which wasn’t expected, or isn’t valid in this context
ok got that, so this works and installs a non-memory based to /dev/sda … fine to boot from, but we want it to run from memory, scenerio dual 128gb boot drives installed as mirrors /dev/sda /dev/sdb
we want to install livefs to the mirror and boot from it instead of usb, but run from memory.
The live image doesn’t install anything unless you ask it to. By default, it’s just a full Fedora CoreOS system running from RAM.
Booting a mirrored live image is outside the functionality supported by Fedora CoreOS. You could probably assemble your own mechanism though: create your mirrored volume, copy the live PXE image into it, install a bootloader, and have it boot the PXE image. These docs describe PXE booting, though you should be able to use any bootloader. See here for more about the live image.