
Containers and Steam: Putting games under pressure | FOSDEM 2020
About this video
FOSDEM 2020 talk from Collabora on pressure-vessel, an experimental mechanism that puts Steam games in containers on Linux. It covers using namespaces to give games their own runtime library stack independent of the host.
Why it appears in the archive
HN references it as the explanation of how Valve uses containers for Linux game compatibility.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
Here's someone from Collabra doing a talk on it [0]. The idea is pretty straightforward, but actually will fill an important niche in the compatibility and eventual archival space. On a higher level note, this shows that Valve is pretty committed to Linux as a concept. I feel that while a second wave of Steam Machines or Steam OS may be a while away, they're certainly making it much easier for gamers to Switch to Linux if they were so inclined. [0] [VIDEO]
Read original comment ↗Valve are basically doing Flatpak on their own. They're using Bubblewrap (made for Flatpak) with their Linux runtimes. See here: [VIDEO]
Read original comment ↗> I'm sure many would happily drop 32bit games support for that. Really? There are still many x86-only games on Steam, tons of which probably won't ever be updated. And if Valve does not make that clear on the Store pages then they will receive part of the blame and support burden. I think what is more likely to happen is for Steam to come with it's own 32-bit dependencies that marshal to the 64-bit system GL/Vulkan/etc. The client itself might be ported to 64-bit too but that would not even be needed at that point. This is already partially the case today - the Steam runtime contains most required 32-bit (and 64-bit) libraries and Steam is already (optionally) using containers for games: [LINK] Presentation on this from 2 years ago: [VIDEO]
Read original comment ↗