I like the concept of sandboxing, of device manager and restricted user, in certain cases it can be really useful to implement, and I’d like to try doing something like that on desktop.

I would install Android directly but desktop apps are usually superior in many ways.

At the same time I think stuff like qubes OS is too much…

Maybe leveraging flatpaks or docker can be a solution, toolboxes too?

I’ve also tried Nixos but I don’t think it is what I’m looking for.

  • Atemu@lemmy.ml
    21·
    3 days ago

    That is not relevant here in any way. That’s a distro made to easily run one app at a time without really caring about data security w.r.t. that app.

    • dajoho@sh.itjust.works
      1·
      3 days ago

      He specifically mentions containerization, Flatpaks, Docker and Toolboxes, which these suggested Fedora Spins are designed to integrate with as tightly as possible, so completely relevant.

      Also, Bazzite is completely the opposite of an OS designed to run one app at once, which means you haven’t tried it before rubbishing it as a suggestion.

      p.s. Don’t take this the wrong way but the phrasing in your comments here make them sound quite aggressive and could lead them to be interpreted in the wrong way. Would you speak to someone like that on the street?

      • Atemu@lemmy.ml
        22·
        2 days ago

        He

        I hate to be that guy but OP gave no indication of their gender. English has the luxury of having a “natural” neutral pronoun; please just use that.

        which these suggested Fedora Spins are designed to integrate with as tightly as possible

        Could you explain what exactly this “tight integration” pertains? AFAIK these are just regular old global-state distros but with read-only snapshotting for said global state (RPM-ostree, “immutable”).
        Read-only global system configuration state in pretty much requires usage of Flatpak and the like for user-level package application management because you aren’t supposed to modify the global system state to do so but that’s about the extent that I know such distros interact with Flatpak etc.

        Bazzite is completely the opposite of an OS designed to run one app at once, which means you haven’t tried it before rubbishing it as a suggestion.

        That is their one and only stated goal: Run games.

        I don’t know about you but I typically only run one game at a time and have a hard time imagining how any gaming-focused distro would do it any other way besides running basic utilities in the background (i.e. comms software.).

        Obviously you can use it to do non-gaming stuff too but at that point it’s just a regular old distro with read-only system state. You can install Flatpak, distrobox etc. on distros that have mutable system state too for that matter.

        Could you point out the specific concrete things Bazzite does to improve separation between applications beyond the sandboxing tools that are available to any distribution?

        It’s true that I haven’t used Bazzite; I have no use for imperative global state distributions and am capable of applying modifications useful for gaming on my own. It’s not like I haven’t done my research though.

        • dajoho@sh.itjust.works
          11·
          8 hours ago

          I hate to be that guy

          That’s okay. Don’t be.

          but OP gave no indication of their gender.

          This is unnecessary white-knight pseudo-concern-trolling designed to derail from the topic at hand. This isn’t a conversation about gender. If I misgendered dontblink, I’ll send 5$ as an apology. You don’t, however, get to choose the language I use, as I equally don’t get to choose yours. Now, back to the Linux discussion:

          Could you explain what exactly this “tight integration” pertains? AFAIK these are just regular old global-state distros but with read-only snapshotting for said global state (RPM-ostree, “immutable”).

          Certainly. That’s essentially absolutely correct. In the case of Bazzite specifically:

          • Distrobox comes pre-installed, enabling application installation inside sandboxed Podman containers with restricted access to /dev. Unlike Toolbox, Distrobox can be configured with different and fully isolated home folders, meaning containers won’t have access to your GPG/SSH keys or other user files unless explicitly configured.
          • ujust is pre-installed (docs), providing helper scripts for various tasks, including easy virtualization setup for virt-manager/qemu/kvm for running completely isolated operating systems.
          • BoxBuddy is pre-installed, a GUI for easy management of distrobox containers, also allowing you to alias/sync .desktop files from sandboxes to your main home folder, allowing you to start sandboxed GUI apps from your normal GNOME/KDE menu.
          • Waydroid integration can be added via ujust, allowing launching of sandboxed, isolated Android apps directly from the desktop environment.

          That is their one and only stated goal: Run games.

          That’s incorrect. While gaming is their primary focus—especially with the “big-screen” edition that boots directly into Steam—Bazzite also offers fully functional, polished desktop environments with thoughtful defaults. For example, even if only an insignificant tweak, GNOME on Bazzite has minimize/maximize buttons enabled by default (unlike Fedora Silverblue). It also supports developer workflows and even isolated, containerized systemd services. (docs). They offer Bazzite editions which boot directly to the desktop environment as default, leaving Steam as only a normal Flatpak application.

          Could you point out the specific concrete things Bazzite does to improve separation between applications beyond the sandboxing tools that are available to any distribution?

          None, beyond having them pre-installed out of the box. But it’s important to distinguish that dontblink asked for a solution, not the solution. I suggested Bazzite GNOME because it provides a nearly complete setup without needing to manually mess with rpm-ostree first. Everything it can do can also be done on other similar immutable systems with a little extra work.