According to this post, once these projects move to bootc, they are going to get rid of layering and allow you to just dnf install what you need.
Recent discussions upstream has consolidated around doing things the Ublue way. Pulling a base image from an upstream registry and using containerfiles to define a system locally. No custom scripts and unit files. No GitHub. Just writing custom changes to a containerfile and having them automatically apply on reboot. Running dnf install @virtualization would add the following line to the containerfile in the background:โ
RUN dnf install -y @virtualization
The powerful thing about build time container image layers like this is that you can do deep customizations like switching out the kernel, changing the login manager, use your own custom boot screen, or redistribute your build by pushing it to a public/private container registry or as the Ublue team shown use container based ci/cd workflows for automated vulnerability scanning against public databases like NVD and CVE.
Seems like it will get rid of a lot of pain points.
Hornet is a Mary sue designed to emasculate bug men.
According to this post, once these projects move to bootc, they are going to get rid of layering and allow you to just dnf install what you need.
Seems like it will get rid of a lot of pain points.