silverblue-site VS firejail

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

bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.

Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.

If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail

Firejail is cool: https://github.com/netblue30/firejail

Linux namespaces/cgroups but nowhere near as heavy as Docker.

I use it when I want to limit the memory of a Python script:

```

Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/

Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case

Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.

This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...

TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.

Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.

Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).

Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":

Firejail does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc

What do you mean by a Firefox container? Do you mean FireJail?