Hi there folks, I’m still learning about Linux and have yet to dip my toes properly in any arch based distro. Have for the moment fallen in love with the immutable distros based on Universal Blue project. However I do want to learn about what arch has to offer to and plan on installing default arch when I have time. But have been wondering why I haven’t heard of any immutable distros from arch based distros yet.

So, am left wondering if there are talks within that Arch community of building immutable distros?

While writing this post I found a project called Arkane Linux, which seem to be very interesting. Does anyone have nay experience with it? Is there a specific reason why immutable wouldn’t be a good idea when based on Arch?

Project: https://arkanelinux.org/

  • Lem453@lemmy.ca
    5·
    6 months ago

    The biggest issue with immutable OSs is the lack of containerized apps. Most devs simply don’t distribute their apps in flatpaks etc. Install fedora atomic. Fist think I want to do is install xpipe to manage my servers. Can’t be don’t in an unprivileged flatpaks. Great layer it on.

    Let’s try seafile next to sync my files and projects…the flatpak is maintained by a random volunteer and most up to date version is from a year ago. Great, layer that in as well.

    Let’s install a command line tool, before it was 1 line, now it’s a whole lot of googling only to discover that the best way is probably to just have a whole other package manager like brew

    The concept is great and it has lots of potential, just it will only work if devs start packaging their stuff in a format that works with the new paradigm (containers)

    • jcarax@beehaw.org
      4·
      6 months ago

      Yeah, I played with Silverblue for the first time a week or two ago, when I decided to move back to Gnome from Plasma. When I realized that I’d need to layer adw-dark to get rid of the light settings panel in Gnome Console, and then layer in aptx and ldac support, and then some drivers for hardware accel in Firefox… I came to undestand that truly approaching this as minimally layering, and instead properly relying on flatpak and toolbx/distrobox wasn’t going to work out. Instead I’m just going to get anxious every time I have to say, ‘well fuck, I guess I have to layer this too.’

      That and I really don’t like the mess of a filesystem. So back to Arch, with some things learned to keep stuff I don’t like out of my base system. I can use a Bazzite-Arch container for Steam, to avoid having to enable multilib, for example. Well, if I can figure out the performance issues, anyway. And I know I’m weird, but I’d kind of like to avoid using AUR on my base system, and Flatpak kind of terrifies me for the reasons you mentioned

      I do look forward to an immutable future, but I don’t think it’s going to make me happy for some time. Maybe Nix or GUIX, but that sounds like a winter project. I know some folks use an Arch base with Nix layered on top, but that rather sounds like the inverse of what I’d ideally want. It seems like the beauty of Nix is that you don’t have to worry about layering, because YOU declare the base?

    • yala
      4·
      6 months ago

      The biggest issue with immutable OSs is the lack of containerized apps.

      Disagree. This is a non-issue for NixOS and Guix System. If anything, what you say only (somewhat) applies to Fedora Atomic or otherwise immature and/or niche immutable distributions.

      For Fedora Atomic (and others that operate similarly), pet containers (read: Toolbx (and later Distrobox)) were originally envisioned as the solution. But, even Nix (and as you’ve noted brew on opinionated uBlue) has been used to that effect.

      Though, yes, I don’t ignore that sometimes you just gotta layer it. Thankfully, as that’s exactly why we got that feature 😉.

      • Lem453@lemmy.ca
        2·
        6 months ago

        I don’t think xpipe would work, it needs too many permissions.

        Something like seafile would work, better than overlaying it I guess but still isn’t park of a package manager with easy auto updates etc like it would be if the devs published to flatpak.

        At the end of the day it’s a lot more work that the promise of opening discover, searching an app and hitting install.

        • biribiri11@lemmy.ml
          3·
          6 months ago

          I know ssh -X works fine in a rootless podman container, and so does waypipe. I’d be shocked if xpipe didn’t.

    • biribiri11@lemmy.ml
      2·
      6 months ago

      Not everything should be flatpak’d. In your case, xpipe (and in the future, waypipe) should always be installed in a docker container containing your normal “mutable” OS. It’s why Fedora is evaluating Ptyxis: when you open a terminal, instead of defaulting to your immutable root, it can be set up to go to a container which has your home mounted but a traditional, mounted root.

      • Lem453@lemmy.ca
        3·
        6 months ago

        Actually yes. Fedora atomic has a system called toolbox that uses podman to encapsulate desktop apps. Flatpak also provides a sandboxed container.

        The idea is to keep the OS and apps separate as much as possible for both security and stability.