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?
The one thing I would like to see more clarity on, is how locally layered packages (currently handled with rpm-ostree) will be handled with bootc; a number of packages can become flatpaks or have flatpak versions. However, not everything works fully as a flatpak or can be easily made into a flatpak.
I realize there are currently technical challenges here, and that any sort of transition process is by no means being rushed out the door.
but still my concern is that rpms outside of the fedora project repos will end up as: unsupported (facing deprecation without replacement), will force independent developers to create limited functionality versions of software, or will simply drive away users and developers from the fedora project due to added package building and installation burdens.
So my question is this: Will the Fedora Project provide the resources the wider open-source community needs to ensure the vast majority of software currently supported continues to be maintained on the platform or will we see a smaller project moving forward?
I realize this is a mean question… but I still believe taking the bull by the horns is better in the long run…let’s have some clarity.
but I still believe taking the bull by the horns is better in the long run…let’s have some clarity.