TL;DR: It's basically a WSL for Linux. Linux subsystem for Linux if you will.
It let's you install and use pretty much any software ever written for Linux, including AUR packages and graphical apps, on any distro you want. You should all give it a try!
Distrobox is probably the best thing ever.
If bread existed in the Linux world, Distrobox would be the equivalent, or better than sliced bread.
It just solves many of the problems that plagued us in the past!
I'm just sick of answering so many comments or posts where people either
- almost dislocate their joints in trying to get some software working on their distro, where it isn't officially supported;
- or choose/ leave a particular distro based on the amount of available packages, e.g. Arch.
**The answer is simple: use fucking containers. **
Before I turned into a weird "immutable distro"-user, I slapped every random install onto my host OS.
After all this shit building up over years, and cluttering my system, it turned against me.
Repos not being available, packages conflicting, weird icons popping up, and more. It was a mess!
If one did that on a server, he would probably get slapped by the Selfhosted-community.
If there's Docker, Podman and more, especially for servers, why don't we use it for desktop too?
Some guy probably thought the same and made Distrobox.
You can just download BoxBuddy as Flatpak and/ or install it via package manager.
BoxBuddy is a graphical frontend, that helps you manage and use your containers. It's pretty new tho and is still in heavy development.
Traditionally, Distrobox is CLI-only, but I can see that changing in the near future.
"Why not just use a VM?"
Those containers aren't isolated and barely draw additional resources. Actually, they're somewhat comparable to Flatpaks.
They provide themselves with their stuff they need, but aren't virtualized. The main difference between Flatpaks and DB-containers for myself is that Flatpaks have permissions.
They can and will interact with your host. For example, if I plug in my phone, I can access it via ADB in my Arch container. Or my Nextcloud-client can open my browser and auto start on boot.
Who needs that?
Everyone. Well, maybe. Depends.
Image distros
Certainly users of image based ("immutable") distros like Fedora Silverblue and other variants of this family, like uBlue (Bazzite, etc.).
While we actually could install every package from the Fedora repo traditionally on our host, this should be avoided.
Steam Deck users would benefit strongly too, since they can only use Flatpaks atm.
People who can't get some packages with their distro
One of the main arguments, why so many users go or stay on Arch, is the AUR.
Often, they have a love-hate-relationship with it. It might break easily if you do something wrong, which is easily done for many users. At the same time, it gives them their niche software they need.
What if I told you, that you can enjoy this huge plus point for Arch on every other distro too, while benefiting from the comfort of your favourite distro?
You can even install an Ubuntu container and use Snaps there if you enjoy using them.
Developers
On the stock Fedora Silverblue, there's Toolbx pre-installed, which does something very similar, but not as good. It's a RedHead product.
On uBlue on the other hand, Distrobox is the default, which is better.
Toolbx' main use case is programming. For devs working with different Python-versions for example and don't wanna risk breaking their OS.
DB does the same, but more.
But why is it so powerful?
You can also export your software to your host.
E.g., the Flatpak version of Nextcloud didn't work well for me. The Arch package on the other hand is less buggy and looks properly.
It's perfectly integrated in my system and I don't notice it at all that it hasn't been installed natively.
This even extends to DEs and TWMs!
You could, for example, create an Arch container only for Hyprland, which you basically can't install on other distros.
And then, you can use said example, or the beta-version of the new Plasma, on OpenSuse Leap.
On uBlue at least, all my containers update themselves too.
Another great thing is the modularity.
You can, for example, just delete the Arch container if it breaks randomly or due to user error, without worrying about losing access to your PC or having to troubleshoot for hours.
All in all, just try it. Trust me.
Yep, exactly that. Simplified, there's only "your stuff" (mostly /var/ and or /home/), and then there's "the OS", which you never interact anyway and is only there to make everything function. Similar to Android.
And when you rebase, you swap out "the OS"-part, but keep "your" stuff.
It's like a clean reinstall, but you don't have to download your Flatpaks, type in your WIFI-password and copy your photos again. Everything else is fresh.
Yes and no.
There is a core image (no DE), yes. And you can install the WM with OSTree too, yes.
But, no. You don't do that. OSTree is basically only there for your individual stuff that needs the privilege of the base system. TLP, drivers, such things. For everything else, it's the last resort.
But don't worry. Here comes the best part: you go to universal-blue.org and create your own image.
You basically use the blank template and tell the "build script" which packages to use.
And then, you can use this custom image, which will be automatically updated by automatic Github build actions. It's basically a spin/ distro you don't have to maintain yourself.
You can try it, it is actually pretty easy. I will do the same soon, and I'm a noob in contrast to you! :)
On traditional distros you have a down-to-top approach, and on immutable ones, a top-to-down. If you want to make bigger changes, you change the image, not your install. Both are customisable, but the one takes another approach.
If you decide to make your own DE-spin, please contact the uBlue devs, so they can add your image to the official list.
If you do that, others can use it too and have the exact same install as you :)
this has blown my mind! it's here i'm supposed to go, right? the only problem i have is with github, since i have moved my stuff to codeberg and this looks way too dependent on github specifically.
i think i might either try Sericea (sadly just default sway, not swayfx) or use NixOS. this is because i don't want to have to learn too much at once, as that tends to be confusing and frustrating.
Update: I installed NixOS on my laptop (secondary pc) to learn it. Took me all day, but tommorrow I'll maybe make a dotfiles repo using flakes.
Here's a starting point I found for doing exactly that: github:Misterio77/nix-starter-configs.