Valve have been cooking! A new Steam Client Beta is available with something quite special for Linux gamers, as Valve work to continue improving Linux gaming.
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).
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
Containers all the way down.
My services are all running in containers, but I’ve some work to do to catch up to your skill level. That said, the above comment is music to my ears with where I am at in the learning process just now, it just resonates. Have a good weekend!
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).
At that point, why not just go for Qubes OS?
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
Containers all the way down.
My services are all running in containers, but I’ve some work to do to catch up to your skill level. That said, the above comment is music to my ears with where I am at in the learning process just now, it just resonates. Have a good weekend!