Support variant of bootc install to-filesystem
omitting bootupctl
, fstab
#949
Labels
area/install
Issues related to `bootc install`
enhancement
New feature or request
triaged
This looks like a valid issue
I'm playing with booting fedora-bootc as a live image. The end goal is a diskless setup where PXE downloads GRUB, GRUB downloads the initramfs and kernel, and dracut (
livenet
module) downloads the root squashfs (remotely built), mounts it as a live image, and lets ostree boot it. I don't need day-two updates. If my understanding is correct, this resembles how Fedora CoreOS runs from RAM.I put together a working proof of concept (below) where I make a disk image with a GRUB boot partition, ESP, boot partition, and root partition, and run
bootc install to-filesystem
on the root partition.bootc install to-filesystem
installs fedora-bootc to the root partition, writesfstab
, and runsbootupctl
to install GRUB to the boot partition. However, I end up deleting the generatedfstab
and disregarding the boot partition, since I really only need the squashfs of the root partition withoutfstab
, and I'll roll my own GRUB config (writing my own/boot/loader/entries/ostree-1.conf
).In other words, this workflow would be much simpler if
bootc install to-filesystem
had an option to only install the container image to a given root, and omit writingfstab
and runningbootupctl
. Are there any considerations I'm not thinking of that would make booting fedora-bootc as a live image a bad idea?Proof of concept
Constructing the squashfs:
Taking it for a spin. This makes a disk image with just a boot partition, installs GRUB manually, adds the squashfs / initramfs / kernel, and writes a config that references them:
The text was updated successfully, but these errors were encountered: