Timothée Ravier

As far as I could see when trying various RAID setups in Anaconda (https://docs.fedoraproject.org/en-US/fedora/f36/install-guide/install/Installing_Using_Anaconda/#sect-installation-gui-manual-partitioning-swraid), they only create a single EFI system partition. So Fedora CoreOS should be the only case...

This is about `testing-devel` and `next-devel` builds right? I already though that was a nightly build and not a per push one so I'm +1 if my understanding is correct.

Things to clarify: - Should we include/exclude runc/crun? - Should we include/exclude skopeo (pulls-in container-commons)?

This is working for me with https://github.com/travier/podman-machine-config

I think it's still worth doing, even if it's not urgent anymore.

Some context for https://github.com/coreos/fedora-coreos-config/pull/774: The use case where we need to run sysusers in the initramfs (https://github.com/coreos/fedora-coreos-config/pull/774) is when you want to declare a system user in a sysusers config...

Here is an example config that should fail: ``` variant: fcos version: 1.5.0 storage: files: - path: /etc/foo user: name: "foo" contents: inline: | # Dummy placeholder - path: /etc/sysusers.d/foo.conf...

We should also probably split the LUKS Storage configuration part into its own page.

Maybe this could be coupled with https://github.com/coreos/fedora-coreos-docs/issues/292

Clearing assignee as I'm not currently working on this.