• 4 Posts
  • 464 Comments
Joined 3 years ago
cake
Cake day: August 11th, 2023

help-circle






  • Qubes is really cool but it uses VM instead of containers, and for its use case you basically have too. Containers isolation at almost no cost come from actually share the underlying kernel and hardware. That isnt isolated enough for data domain seperation thay qubes is built around.

    That is one reason i have multiple clusters actually, and the confidential container effort is actually light weight VMs with tools to intergrate them with the network of the host correctly (and multikey memory encryption to fully enforce the boundary). I havent goten around to deploying an app like that yet myself though




  • I run most of my software in containers. Firefox is in a flatpak. My terminal shells are all containers using distrobox. My homelab services are all containers. My few VMs (i run a few vituralized rke2 clusters, sometimes a test version of my baremetal harvester cluster, and test versions of my desktops)? Also running in containers. My desktop OSs are also containers (ublue, SteamOS, and SUSE Elemental).

    The future is now old man! :p

    But honestly linux namespaces and overlay filesystems are the bees knees. Create reusable layers of filesystems, use just the ones needed for a given app/service. Expose just what a service or app needs to for a given function. You end up with an extemly portable, and consistent system that has cleaner seperations of concerns. For basically free. From an app dev perspective you remove a whole matrix of supported configurations to worry about (distro/version/packages installed/etc).








  • That is a runtime that some flatpaks use as well.

    Gnome and KDE as projects are a bunch of things, from login managers, to compositers, desktop UIs, and user application (like Gnome “System Monitor” or KDEs “Plasma System Monitor”).

    You can actually mix and match some pieces and they just work, but especially the user apps because both teams put in work for interoperabilty or Freedesktop standarization.

    So you can have an app that uses KDEs shared libs and an app that uses the Gnome projects libs on the same issue with rarely any issue. Even more so with flatpak since the all of the files those apps see are in what is called an overlay filesystem, so your kde apps get a layer of files jist for KDE apps to build off of and gnome apps get a layer of files just for them to use. In flatpak these are called runtimes. That is what is being updated here.