Running Steam in a systemd-nspawn Container
Pack it up, pack it in
Systemd has a cool thing called nspawn which is a mechanism for running things in containers. The Arch Wiki puts it thus:
systemd-nspawn may be used to run a command or OS in a light-weight namespace container. It is more powerful than chroot since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and the host and domain name.
systemd-nspawn limits access to various kernel interfaces in the container to read-only, such as /sys, /proc/sys or /sys/fs/selinux. Network interfaces and the system clock may not be changed from within the container. Device nodes may not be created. The host system cannot be rebooted and kernel modules may not be loaded from within the container.
I will tell the tale of how I created a container in which to run Steam (and other things).