From this Fedora release article I see that FCOS is going to bootc and using OCI to deliver images.
We’re also moving forward with our bootc enablement story. Fedora CoreOS is now buildable from a Fedora base bootc image using a Containerfile, instead of needing to be composed with a custom tool. That means anyone with podman can build the Fedora CoreOS image, whether manually or via CI/CD automation.
Fedora CoreOS (FCOS) is also changing how it’s issuing updates to users in Fedora 43. Instead of using an OSTree repository, FCOS updates will be delivered exclusively as OCI images. FCOS 42 provided both OSTree repository and OCI registry as a transition for users. In FCOS 43, the OSTree updates are disabled entirely.
Pretty excited about this but there’s no follow on link. I am wondering if there is a more in-depth article somewhere that discusses what is being done. Also, with this is it now possible/desired to build an image of our own that bakes in essentially an ignition instead of calling it later on?
I suppose it wouldn’t be a big deal either way but I’m curious. Along with that, would it then be possible to just point it at a different registry that is taking the FCOS base image and layering it with whatever changes to pull from when it needs an update?