this post was submitted on 23 Aug 2026
36 points (97.4% liked)
Linux
14775 readers
311 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
NixOS is like the opposite of Bazzite. On Bazzite you don't configure anything, so no need for a git repo or anything. Just install the OS and start using it. (Bazzite also supports rollbacks btw).
Having to configure and manage every little thing, is like the opposite of the ethos behind Universal Blue distros like Bazzite.
On fedora atomic desktops /etc is completely writable so you can configure some things. And using rpm-ostree it is possible to do weird things too
But you should have a look at how Bazzite is actually built. A bunch of containerfiles, scripts, ujust files, ... not hard to understand but kinda messy. And you kinda need a server. On NixOS you do this on your machine.
And do note that there are presets online and people help you set things up.
I'm aware of how fedora atomic distros work, and that some things are configurable. My point is that a Bazzite user doesn't need to touch the cli or any config file, to just start using their desktop. I think those of us that have been using Linux for years, forget how rare it is for Windows and Mac users to touch the cli or config files. That's the experience that the Universal Blue ecosystem seeks to provide.
I prefer containerfiles tbh, because I use them for my server too.
Technically you could set up the ublue infra on your own machine. Building and serving container images inside a container on your own host. Though it's more overhead than NixOS I'm sure.
I'm aware but from what I've heard it's similar to docker compose configs. You can't just paste them in and expect everything to work. You'd have to copy one person's config for their entire desktop, and never deviate. At that point you may as well just use rpm-ostree, which is designed for this sort of workflow.