I'm curious about the practical benefits rather than just the technical design. Does an immutable or atomic distro make recovery easier, and how much does it get in the way of installing apps or customizing the system?
What are the everyday tradeoffs of an immutable Linux distro?
Answers
The main appeal is having a more predictable base system. On an atomic distro, updates are applied as a system deployment rather than changing the running system package by package. If an update causes trouble, some distros let you boot back into a previous deployment.
That doesn't mean the same update would have broken a conventional distro. It's more about having a convenient recovery option when something does go wrong. Check how many previous deployments your chosen distro keeps and how its rollback works.
Reply to this answer
App installation is the bit to look into before switching. Flatpak can cover a lot of desktop applications, and a container tool such as Distrobox can provide a conventional package manager for development tools and command-line utilities.
Some software still needs to be installed on the host. On Fedora Atomic variants, for example, you can layer packages with rpm-ostree, but that changes the system deployment and generally calls for a reboot. Instructions written for a regular distro may not translate directly, especially when they tell you to install packages or edit files in the base system.
Mirelka-2v:
So the friction depends partly on whether the apps and tools I need work as Flatpaks or in a container?
p.482+fusecaddy:
Right. It's worth checking the awkward cases too, particularly tools that need host integration or access to hardware.
Reply to this answer
If you like the defaults, this can be a pretty low-maintenance setup. If you enjoy changing the base system itself, you'll probably notice the restrictions sooner. I'd pick a distro that already gets the desktop and hardware support close to what you want, rather than assuming every conventional customization guide will work.
Reply to this answer
You don't need an immutable distro just to have a way back from a bad update. A conventional installation can use filesystem snapshots and backups too, while keeping the usual package management workflow.
The tradeoff is that you need to set up and understand those recovery tools. Atomic systems can make deployment rollback part of the normal workflow, but their update sizes and download times can also be a drawback. The better fit depends on which inconvenience bothers you more.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Kavi:
A rollback isn't a replacement for backups. It may restore the system deployment without restoring your personal files or undoing changes in your home directory.