silverblue-site VS distrobox

Fedora; from its 'flagship' Workstation, to their glorious Spins and their Immutable Desktops

Fedora Silverblue - pretty well-known at this point, but it’s championing immutability

Couldn't have said it better!

An example of an installable immutable OS is Fedora Silverblue. Notably, you can change the "distro" flavor of Silverblue to try out KDE and then just flip back to Gnome. Each change is seen as an "update" that just moves you over to the new GUI. The article below explains a bit more.

I guess something like Fedora Silverblue might offer you something (to paraphrase) "stupid proof". For example, in this case the rpm-ostree rollback command would have been sufficient. Disclaimer: rpm-ostree builds images, therefore it's by necessity slower than apt. Futhermore, until this change is merged and deployed you'd have to reboot for the changes to apply. You might want to look into Distrobox as well, perhaps it can solve your problems without having to change your distro.

However, I'll add one more that I'm especially fond of. It's one of the most 'stable'\1]) Linux desktop systems\2]) without sacrificing access to the latest kernel-updates and packages. It comes bundled with everything\3]) necessary for productivity right out of the box and is built on top of the fundamentals laid by Fedora's Immutable Desktops. Allow me to introduce uBlue; I know that I'll undersell it regardless, so I recommend you to check the provided link instead.

the immutable desktops offered by Fedora; which would be Silverblue, Kinoite and Sericea (special mention goes to uBlue)

OS: Fedora Silverblue

Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)

I use containerized versions of things, ubuntu and chainguard images mostly.

You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...

https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...

Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md

For such cases you might use something like this: https://github.com/89luca89/distrobox

Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).

1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39