Hacker News Reader

Comment by LelouBil | Hacker News Reader

Great distro ! I have been using it for the last 2 years on my Framework laptop 16 without any issues. I even have a "fork" of sorts that adds Hyprland + all of my "desktop" config, which I think as being part of the OS.

I really think immutable distributions are the future of linux desktop, and maybe distributions that use OCI images, beacause they are a lot easier to work with than say, NixOS for example.

If you want to have your custom bazzite, you just do a "FROM bazzite:<whatever-version-you-want-to-pin" and add stuff you want.

Of course, you loose a bit of the reproducibility, since usually container images do not pin packages (and maybe other reproducibility issues I am not aware of) but it is way easier to work with.

View on HN

I'm an https://getaurora.dev user and I agree uBlue is awesome. I'd like to create a custom image too, but it doesn't seem quite as easy as you say: https://youtube.com/watch?v=IxBl11Zmq5w

While the video is long, the actual process of setting everything up only took me about 20 minutes. The template they offer is extremely convenient.

I will offer a second positive but more reserved data point. It took me closer to a day to get my custom Bazzite build working.

Switching over to my images using bootc failed because of what I eventually tracked down to permissions issues that I didn't see mentioned in any of the docs. In short, the packages you publish to Github's container registry must be public.

Another wrinkle: The Bazzite container-build process comes pretty close to the limits of the default Github runners you can run for free. If you add anything semi-large to your custom image, it may fail to build. For example, adding MS's VSCode was enough to break my image builds because of resource limits.

Fortunately, both of these issues can be fixed by improving the docs.

There's also BlueBuild [1] which abstracts the process of building your own images away further into yaml configurations.

It takes away a tad bit of the direct control of the process, but covers the majority of things you would want to configure.

[1] https://blue-build.org/

The actual process for the image is really just what I said. In the video he sets up a github actions automatic build, and adds signing with cosign (which are also all steps you really want to do) but to have custom stuff in your base os is really as easy as a Dockerfile (or should I say Containerfile ?)

I learned about Aurora from a HN comment some weeks ago, and it has been so awesome. I really haven't been as impressed with a distro since the first ubuntu. Its just a rock solid base, awesome defaults, and kde being delightful.

Immutable is very good for new linux users but I personally don't like the restriction and find rpmostree extremely slow to install literally anything. It does make sense to use immutable distros in routers, firewall, etc

I try not to use rpmostree to install anything (only steam-input, codecs and nvidia drivers), and rely on homebrew, appimages, flatpaks and toolbox for my app needs. It works so far...

There is something about immutable linuxes that feels right, and I cannot pinpoint why exactly, but it's like things are segregated correctly.

It’s probably that they’re near impossible to break or end up with an unusable system.

I have disabled read-only mode and I use pacman like you would in a normal Arch system. Makes it a lot easier to install packages

Reply on news.ycombinator.com