Why use immutable Linux ? And which one ?

Yes, though keep in mind containers aren’t like VMs so the hardware isn’t virtualized or anything. The root system and everything in it is still immutable as well. In usage, it doesn’t matter for the container but it isn’t changing the root since what is writable to the container is outside of the root.

Using containers this way is the way Silverblue was intended to be used for by the user and pretty much any other immutable distro of note.

permalink

report

parent

[ - ]

atzanteol@sh.itjust.works

2 points

9 months ago

Yeah - I’m quite familiar with containers. I just don’t see the value they’re adding here. Maybe for experimental things or “project-specific” stuff. but otherwise don’t you just end up maintaining a container same as you would your “host OS” in a non-immutable distro?

permalink

report

parent

[ - ]

Kid_Thunder@kbin.social

2 points

9 months ago

Your immutable OS stays stable. For example, running a sudo pacman -Syu with a bunch of stuff from AUR in your Arch container for example will not bring down your OS or otherwise make it unstable. The immutable image you first install has been tested and it is the same image as the testers – same with the upgrades and updates, so long as you don’t overlap the image with rpm-ostree in this case.

Immutability keeps your OS stable and if something does happen to go wrong, you just roll it back.

If that isn’t something you need/want then that’s not something you need/want.

permalink

report

parent

[ - ]

atzanteol@sh.itjust.works

5 points

9 months ago

It’s definitely not - I’ve just been trying to understand the problem it solves for others though and see if it is something I would be interested in.

From what I can tell I can get all of the advantages in a “mutable” distro (flatpak, distrobox, etc.) without the overly-complex “immutable host” stuff.

I honestly don’t get the fear of “some random update ruins your OS”. Perhaps because I’m not an Arch user.

report

[ - ]

3 points

9 months ago

Yeah those don’t go on your host they go in containers.

permalink

report

parent

[ - ]

atzanteol@sh.itjust.works

3 points

9 months ago

So I use non-immutable distros in containers to make up for the failings of the immutable host OS?

permalink

report

parent

[ - ]

j0rge@lemmy.ml

3 points

9 months ago

You use containers for your tooling, you purposely don’t touch the host operating system, that’s the entire point.

permalink

report

parent

[ - ]

atzanteol@sh.itjust.works

4 points

9 months ago

I can do that in Ubuntu… I’ll admit I simply don’t see the point. Immutable distro users seem paranoid about “some random update messing up their base OS” for some reason and I guess this suits their purpose. I just don’t see that as a problem.

permalink

report

parent

[ - ]

j0rge@lemmy.ml

4 points

9 months ago

Most people aren’t system administrators and they end up with broken computers for the most basic tasks. It’s one of the major reasons why people hate using Linux desktops.

And even if you’re an experienced sysadmin you can’t account for the entropy that accumulates on traditional OSes. 18.04 -> 20.04 -> 22.04 doesn’t end up being the same as a 22.04 clean install. This is a huge problem, especially for people who don’t know how to manage linux systems. And the people who do manage systems at scale don’t want that behavior either.

I go over this in this video: https://www.youtube.com/watch?v=hn5xNLH-5eA

But day to day I’m in an ubuntu container and using “normal” package management, I just don’t do it on the host.

permalink

report

parent

[ - ]

atzanteol@sh.itjust.works

3 points

9 months ago

But day to day I’m in an ubuntu container and using “normal” package management, I just don’t do it on the host.

If you kept a basic minimal Ubuntu host it would be trivial to maintain. And you can still do your “toolbox” stuff on top of it. No weird immutable stuff needed.

I just don’t see the point. You want new users to understand containers. And to keep track of all the containers they maintain - possibly with different distros and using different things. And remember the difference between them and what is installed in each. Or just maintain one big container which is exactly what they would do normally anyway.

permalink

report

parent

Show more comments

[ - ]

PipedLinkBot@feddit.rocksB

1 point

9 months ago

Here is an alternative Piped link(s):

https://www.piped.video/watch?v=hn5xNLH-5eA

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I’m open-source; check me out at GitHub.

permalink

report

parent

Show more comments

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Why use immutable Linux ? And which one ?

Linux

!linux@lemmy.ml

Rules

Related Communities

Community stats

Community moderators