boxkit VS base

https://universal-blue.org

Using the Bazzite image has replaced Windows for me. Basically everything works.

There are a slew of images built on Fedora Silverblue and a lot of them are very interesting. The ability to rebase in and out of base images safely and atomically is really powerful and liberating. If you haven’t tried an “immutable” distribution, I would highly recommend it. It really does feel like the most logical way to run Linux with zero fuss and maximum flexibility and safety,

https://universal-blue.org/

There isn't something completely like that, but Fedora Silverblue comes really close (and [Universal Blue](https://universal-blue.org/) pushes it slightly closer)

Once installed run the Universal Blue rebase script to make the Kinoiite OS more user friendly. (https://universal-blue.org/)

I'm thinking about Silverblue and Kenoite. Especially, I'm looking at the Universal Blue project. UBlue, because creating your ISO is dead simple because it starts from an OCI image declaration (docker compose).

I'm on a https://universal-blue.org/ -based "custom image" of Fedora Silverblue and I love it. In my image, I ship some essentials software and other things that are just easy to have in there like fonts, plus a script for installing gnome extensions. Then I have a Nix home-manager -based shell configuration containing some common developer tools as well. The bulk of the (GUI) software I use comes as Flatpaks, and my development environment is a distrobox arch container.

I've set all updates to be automatic and almost never have to worry about them. I am on the :latest tag and my computer updates between major versions automatically, and I haven't had any breakage yet. I feel pretty confident in the stability of my system and feel like were the disk to corrupt, I could get back up and running with the exact same setup very quickly.

Hi! I worked on this with some friends over the past two years or so (we had to work on the generic tooling first: https://universal-blue.org/)

I'm happy to answer questions you might have! Thanks for checking it out! (I'll be at KubeCon Chicago with stickers if you want the live demo on a Framework 13)

This is actually run my computer, with a fedora-silverblue based image but my CLI is running alpine images.

So I made a little kit so anyone can do this on any linux so you can try all the cool stuff in there without the downsides of running a less popular configuration on the bare metal.

And since it's Alpine it's always a fast download vs. a heavier container.

https://github.com/ublue-os/boxkit

Like you mentioned, rpm-ostree is meant to be a fallback after non-working options like, in order, flatpak then distrobox/toolbox. But that doesn't mean it can't be used. Keep in mind this is simply a rule of thumb to increase security, stability and rpm-ostree performace, but it's still just a rule of thumb. Silverblue is very flexiible, and I have roughly 600 overlays and while rpm-ostree is slow, the only thing I really do with it is upgrade those packages installed with it, now that my system has the packages I need. Since this can be done automatically (See "man rpm-ostreed.conf") and the system is immutable, the only intervention required is rebooting when necessary (Such as if there's a fixed vulnerability or a new feature update you want). The other nice thing about auto-updates and immutability is that Silverblue is more resistant to breaking while running do to an update of an important system library or the like, since the library isn't even "visible" until the next boot, when those things it depends on are all already setup to use the new version. I also recommend checking out Jorge's flatpak automatic update systemd .timer and .service filese over at https://github.com/ublue-os/base/tree/main/usr/lib/systemd/system and downloading them and using sudo (From a Silverblue terminal) to put them into /etc//systemd/system, doing a "sudo systemctl daemon-reload" and "sudo sytemctl enable flatpak-system-update.timer" . This will update your flatpaks for you. In my opinion, between rpm-ostree auto-updates flatpak updates, you'll have a much smoother experience.

You'll see that the base image installs flatpaks as a post-install step. I really tried to work around this limitation, but haven't been able to via the OCI approach.