I’m considering trying out an immutable distro after using Tumbleweed for the last 6 years.

The two major options for me seem to be Fedora Kinoite or uBlue Aurora-dx

My understanding is that universal-blue is a downstream of Fedora Atomic

So, the points in favor of Kinoite is sticking closer to upstream, however it seems like I would need to layer quite a few packages. My understanding is that this is discouraged in an rpm-ostree setup, particularly due to update time and possible mismatches with RPMFusion

uBlue Aurora-dx seems to include a lot of the additional support I’d need - ROCm, distrobox, virt-manager, libratbag, media codecs, etc. however I’m unclear how mature the project is and whether it will be updated in a timely manner long term

I’m curious what the community thinks between the two as a viable option

  • j0rge@lemmy.ml
    23·
    5 months ago

    I’m unclear how mature the project is and whether it will be updated in a timely manner long term

    ublue and bluefin co-maintainer here, we’ve been around for a while now (3rd birthday coming up!) and have been around in a more unofficial capacity for longer.

    Bluefin is feature complete and is in maintenance mode, it’s just going to get updated in perpetuity to 41, 42, etc. We invested in automation first so most of the maintenance is automatic and it doesn’t take much for our team to do it. Right now most of our major ticket items are waiting for things to finish landing in upstream Fedora, most of which are targetted towards F41. A good portion of the team have been around in OSS for a long time and a bunch of us work in the industry and depend on Bluefin for our jobs, so much so that we have a great working relationship with Framework, so we’re supporting those laptops as a community option for them.

    Aurora is relatively new, coming in just as Plasma 6 landed in fedora. Most reports with issues we get for it are things like it being a new major release, wayland/nvidia issues, etc.

    Hopefully that answers some of your questions, if you have more feel free to ask!

    • ozymandias117@lemmy.worldOPEnglish
      3·
      5 months ago

      Hey! Thanks!

      I’ve installed Aurora to my new drive based off the comments here so far, and it’s been pretty smooth bringing my configs over :)

      Immutable is new to me, so I’m wondering how you manage host daemons and cli applications, such as mpd for music and password-store for password management

      Is the best practice to keep one Fedora <current release> distrobox with them?

      Also, are there any issues with upgrading a distrobox to a new major release over time?

      So far my mindset has been make sure I don’t layer anything, but maybe some things like mpd do make sense to layer?

      I also see brew as another option. Perhaps that’s the preferred way for those types of tools? However, it seems like the system upgrade script updates distrobox and not brew?

      Sorry for the rambling question - just trying to understand best practices with an immutable distro 😅

      • j0rge@lemmy.ml
        8·
        5 months ago

        Immutable is new to me,

        It’s best to ignore the whole “immutable” thing as most of the discussion around that is conflating a bunch of other concepts and it just leads to confusion. When it comes to things like host daemons, these systems are designed to deploy daemons the same way as cloud servers, so for mpd it’d be running the service as a container. A quick search of /r/selfhosted shows some options, but I’m on the road so don’t have time to recommend a specific image, but generally speaking anything server related is done via containers.

        I use the 1password firefox plugin for my password management. There still isn’t a flatpak portal that allows flatpaked password managers to talk to flatpaked browsers, that can be a pain point to some people depending on your use case.

        As far as how you manage your distroboxes, that’s up to you. We differ from fedora here where they default to “just use toolbox” for everything, whereas we default to “just use brew” for everything. I keep an ubuntu and fedora distrobox in case I need to check something from those distros, and arch is a popular choice. If you’re happy with your existing distro but want the reliability of atomic updates then this is a good option. For most new users I recommend not caring about distrobox, most of that stuff is for developers or people that know how to linux already and know exactly what they want.

        Also, are there any issues with upgrading a distrobox to a new major release over time?

        Containers are designed to be ephemeral, so that you can recreate them on the spot when something goes bad. So I never upgrade boxes, I recreate on the spot using my custom configs. That way I have the same experience on all my machines and when something breaks I don’t lose any time setting things up again. Distrobox assemble is awesome for this: https://github.com/89luca89/distrobox/blob/main/docs/usage/distrobox-assemble.md

        So far my mindset has been make sure I don’t layer anything, but maybe some things like mpd do make sense to layer?

        I don’t really layer anything, I use everything via containers or brew. Generally speaking some people might have a few things they have no choice to layer - a good example is a VPN provider that doesn’t provide a wireguard config for network manager and instead you have to layer some 3rd party app. But it’s also not the end of the world, updates will take longer but 99% of the time I’m asleep when that happens or it happens in the background and is transparent to me. The more you layer the more maintenance you’ll have to do when you do upgrades, so if you end up adding a bunch of 3rd party repos it’ll behave the same way as a traditional distro and likely need to be babysat.

        The system will update all your boxes and your brew packages as well, so whichever one you use you’ll never be out of date. Hope this helps!

      • cakeofhonor@lemmy.world
        2·
        5 months ago

        One thing you can check out is quadlet, which is podman containers running as systemd services. You just basically put the .container files in the right directory and sytemd will pick them up and run them for you. I have syncthing and zerotier running like this.

        I don’t really think you need to layer anything unless you’re doing virtualization, but I haven’t really looked into that yet.

        • ozymandias117@lemmy.worldOPEnglish
          1·
          5 months ago

          Thanks! That sounds like exactly what I’d want to run mpd. I’ll check it out

          For virtualization, I’m all good since I went with uBlue instead of Silverblue for now - the developer images come with lxc/lxd/qemu/libvirt :)

  • Fliegenpilzgünni@slrpnk.net
    15·
    5 months ago

    Short answer: use uBlue.

    Longer answer:

    Even though uBlue is technically “downstream”, it also isn’t. uBlue builds its’ packages automatically, and you are never more than a few hours (1 day max for huge updates) away from upstream. It feels more like “sidestream” (if that word exists?).

    One reason it exists is, as you already said, because layering takes quite some time.
    At least I personally don’t wanna use stock Fedora (Atomic) and would install some codecs, tweaks and such anyway, and uBlue does that already for me.
    Update time doesn’t matter anymore for me, because uBlue updates itself automatically in the background. Silverblue doesn’t do that afaik.

    Depending on how “custom” your system should be, you can take a look at the uBlue builder, where you can create your own image based on already existing ones if you like.

    The cool thing about Fedora Atomic is, that you don’t have to stick to anything. If you don’t like something anymore, you can rebase in less than two minutes without any hassle and jump from image to image, no matter if it’s an official one (e.g. Silverblue) or some obscure uBlue image.

  • GravitySpoiled@lemmy.mlEnglish
    8·
    5 months ago

    I can’t say specifics about aurora-dx. Aurora got added to the official bluefin repo, I don’t think it’ll go away any time soon. https://github.com/NiHaiden/aurora if it becomes obsolete, just rebase to another atomic variant and layer your packages. It’s hassle free and only one reboot (and one pin for backup) away.

    You shouldn’t layer any random package. You shiuld layer packages that you need and are useful for the system. Even if those are 100 packages. If you need them, you need them. Some packages can be installed via distrobox but you know that already, I guess.

    • ozymandias117@lemmy.worldOPEnglish
      1·
      5 months ago

      How does bluefin fit in the dependency chain here - is this just the repository that builds official uBlue images?

      Part of my confusion is trying to understand how these projects are related to each other

      Edit - oh, I guess bluefin is the Gnome variant

      • Malcolm@lemmy.world
        1·
        5 months ago

        If I understand it correctly, Bluefin was just the first downstream uBlue variant like Aurora that had the various goodies built into the images. Bluefin effectively being the Gnome version of Aurora. I think it was simpler to tie the Aurora builds into the existing Bluefin pipeline for generating images and packages.

        I highly recommend Aurora (dx) if it sounds like it fits the bill for what you’re looking for. After starting out with Kinoite and rebasing on Aurora-dx, the latter just feels like Kinoite with all of the desired additional packages already baked in, and some great additional shell scripts for convenience.

        Rebasing sounded intimidating but it was literally just a simple shell command and a reboot. One additional command if you want to hang onto the previous image the way you had it. Rpm-ostree is pretty magical.

  • Destide@feddit.ukEnglish
    6·
    5 months ago

    I’m using Aurora-DX and it has such great tooling for what I wanted from Silverblue for my day-to-day work. Never had any issues, and having easy VM’s and Distroboxes has been great for different projects. As primarily python dev, it’s awesome not having to faff with dependencies.

  • boredsquirrel@slrpnk.net
    61·
    5 months ago

    uBlue f**ed up their site a while ago, they had a huge list of images.

    You can just use their kinoite-main image, which is what I do. It has Distrobox, homebrew and a few more things.

    Here is an archived site

    Use kinoite-main:latest and you will even get automatic version upgrades without a problem.

    You can still rebase, you know? I tried Aurora and it was not for me, back on normal Kinoite.

    But for sure it is a bit annoying to layer. But no issue. I layer 20 packages or so, 300 with dependencies, and all is fine.

    I dont know about ROCM, their hardware enablement to my knowledge is just about NVIDIA, Asus and other proprietary stuff.

      • boredsquirrel@slrpnk.net
        1·
        5 months ago

        Interesting.

        Give it a shot, Aurora is fine. May have some packages you dont need, but it is fine.

        They remove Firefox for whatever reason, which makes no sense. The Librewolf and Firefox Flatpaks are probably okay, the Librewolf RPM is completely broken

        • quarterlife@lemmy.sdf.org
          3·
          5 months ago

          We remove Firefox because having it on the image is a security hazard. You want your browser to update more often than your operating system.

          We prefer the flatpak, but if for some reason you need the RPM I would suggest installing it with distrobox.

          • boredsquirrel@slrpnk.net
            1·
            5 months ago

            a security hazard.

            Okay?

            You want your browser to update more often than your operating system.

            Then why do you base on Fedora and have daily auto updates by default?

            I shutdown my laptop every day and update every day. That is fine for me.

            Fedora Firefox has some hardening flags that official Firefoxn has not. It is built for Fedora and works really really good.

            I did benchmarks some time ago and it is also actually very performant.

            Flatpak Firefox does not have the ability to create user namespaces for tab process isolation. This is due to all Flatpaks using the same badness-enumerating seccomp filter, there is no additional hardening possible and they still block userns creation.

            Firefox can still isolate tabs via seccomp-bpf but this means it has 1 of its 2 security barriers removed when using a flatpak.

            Seeing browsers as an app, it is good to have additional security from the browser to the OS, by sandboxing via flatpak.

            But seeing the browser as a platform, passwords, bookmarks, credit card details etc may all be stored in there and a sandbox escape not necessary to steal peoples stuff.

            Removing Firefox prevents people from reinstalling it (due to the rpm-ostree bug), and apart from the tarball (which has no desktop integration and is some random binary ran from some random location, likely without SELinux protection (unconfined users)) it is the best browser on Fedora.

            installing it with distrobox.

            This makes no real sense.

            Pro

            • it can update separately from the OS
            • it works even with the current rpm-ostree bug
            • it is the Fedora RPM
            • it is kinda isolated from the root OS

            Con

            • updates are not automatic and need to be configured
            • not sure if it has access to user namespace creation because it already runs in a user namespace container
            • it adds additional boot time and constant RAM usage due to having a container
            • distrobox does not allow Fedora DNF system upgrades so you need to nuke it and reinstall on a version change (at least every 13 months)

            Using the tarball and placing it in /var/usrlocal/bin/ may be better. But still cumbersome.

            The solution, even if you want to remove it, is having these issues solved, or this rpm-ostree bug fixed.

            • quarterlife@lemmy.sdf.org
              3·
              5 months ago

              Distrobox updates automatically on Bluefin and Bazzite.

              In this case we disagree with Fedora, Atomic Fedora should not have Firefox in image. It does not matter to us what they do, we explicitly remove it.

              If you like the way Fedora builds their Firefox RPM, that’s all the more reason for you to use a fedora distrobox.

              I shutdown my laptop every day and update every day. That is fine for me.

              Irrelevant. Not everybody does. Some people pin an old image due to a bug and sit on a far older image. If you had it your way, they’d be using a week or month old build of Firefox – that’s unacceptable.

              Removing Firefox prevents people from reinstalling it

              Good. I can promise you if that gets fixed and I have a way to continue to prevent it, I will.

              Flatpak Firefox does not have the ability to create user namespaces for tab process isolation. This is due to all Flatpaks using the same badness-enumerating seccomp filter, there is no additional hardening possible and they still block userns creation.

              This is an issue for Mozilla. They are happy enough with the state of the Flatpak to not only verify it, but list it on their website. Unless you’ve got a CVE for the Flatpak version of Firefox I don’t see any point in even engaging with this argument.

              • boredsquirrel@slrpnk.net
                1·
                5 months ago

                Distrobox updates automatically

                True, forgot that you use topgrade

                Atomic Fedora should not have Firefox in image

                There are many relevant issues and it is not a clear choice.

                Irrelevant. Not everybody does.

                Yeah and nobody knows about user namespaces or seccomp filters. This is about at least 2 user groups and one is not necessarily more important than another.

                It is again not a clear choice.

                a way to continue to prevent it, I will.

                * in your opinionated images, I hope.

                You start to sound like a GrapheneOS dev. It makes no sense to prevent users from reinstalling removed packages.

                Which btw also include the Fedora Flathub repository.

                • boredsquirrel@slrpnk.net
                  1·
                  5 months ago

                  You also didnt answer to the security issue of removing an entire sandboxing layer, or to the point about not being able to upgrade Distroboxes.

                  Do you solve the second problem by building a latest distrobox container following the uBlue releases?

                • quarterlife@lemmy.sdf.org
                  1·
                  5 months ago

                  Which btw also include the Fedora Flathub repository.

                  We no longer touch the repos as Fedora is now in agreement with using Flathub.

                  You start to sound like a GrapheneOS dev. It makes no sense to prevent users from reinstalling removed packages.

                  It’s for user security. I have no interest in debating this decision, my reasons are outlined.

    • ozymandias117@lemmy.worldOPEnglish
      1·
      5 months ago

      When I check out the ISO for microOS, it lists microOS Kalpa as “alpha”

      Is it ready to be used as a primary install?

  • minnixAEnglish
    35·
    5 months ago

    So, the points in favor of Kinoite is sticking closer to upstream, however it seems like I would need to layer quite a few packages. My understanding is that this is discouraged in an rpm-ostree setup, particularly due to update time and possible mismatches with RPMFusion

    It’s not only discouraged but often times it’s system breaking. I used Kinoite for a year before I just became too frustrated and gave up. The first thing I learned though was to stay away from package layering because it tended to break things more often than not. Basically if you can’t find or build a flatpak and you don’t want to use toolbox all the time, just stick with workstation. Immutable is great when deploying to multiple servers or locked-down corporate workstations, but it makes no sense for your personal setup especially if you’re already familiar with Linux.