Difference between revisions of "Steam"

From Funtoo
Jump to navigation Jump to search
Line 28: Line 28:
# ##i##rc-update add nvidia-container default
# ##i##rc-update add nvidia-container default
  ##g##*##!g## nvidia-container added to runlevel default.
  ##g##*##!g## nvidia-container added to runlevel default.
#
# rc
}}
 
=== User Setup ===
 
When using docker, you will be starting the Steam container as a regular user account so the container can inherit the connection to
your X server. You will want to make sure your user account is in the {{c|docker}} group:
 
{{console|body=
# ##i##gpasswd -a drobbins docker
Adding user drobbins to group docker
}}
 
You will need to log out and log back in for this group change to take effect.
 
=== PulseAudio Setup ===
 
In order to allow the container to connect to PulseAudio, you will of course need to be using PulseAudio, and then you will also need to enable support for UNIX socket connectivity in PulseAudio. This can be done by adding the following to {{f|/etc/pulse/default.pa}}:
 
{{file|name=/etc/pulse/default.pa|body=
load-module module-native-protocol-unix auth-anonymous=1
}}
 
Once this is done, you should restart your user's pulseaudio daemon for this to take immediate effect:
 
{{console|body=
$ killall pulseaudio
}}
 
Once this has been done, you should be able to see a {{c|native}} UNIX socket in the PulseAudio run directory. This socket will get mapped into the container:
 
{{console|body=
$ ##i##ls /run/user/$UID/pulse/
native  pid
}}
}}

Revision as of 00:41, October 24, 2019

Steam is a content delivery system and ecosystem for gaming, developed by Valve Software. It offers hundreds of games, from popular ones such as DOTA 2 to many other less popular and even obscure community games. Steam runs on Microsoft Windows, MacOS, and also Linux.

History on Funtoo

Through Funtoo Linux 1.2, it was possible to play Steam directly under Funtoo. However, with the move to Funtoo Linux 1.3, 32-bit support was dropped from Funtoo, and Steam is currently dependent on a host of 32-bit libraries. Thus, Steam no longer worked under Funtoo directly. Howevever, it is still possible to run Steam under Funtoo via use of containerization technology.

Steam in Docker

This page will currently document the setup of Steam running on NVIDIA hardware, with documentation for non-NVIDIA hardware to follow shortly.

To run Steam on NVIDIA graphics, with full PulseAudio sound, docker with NVIDIA support will be used.

Host Setup

To get your host ready to run Steam, emerge the following packages:

root # emerge -av --jobs docker nvidia-container-runtime nvidia-docker

You will also want to ensure that you have NVIDIA proprietary graphics running in a graphical environment on your host. Please ensure that you have x11-drivers/nvidia-kernel-modules-435.21-r1 or later installed on your host, and that you don't have any special permissions settings in /etc/modprobe.d.

Next, you will want to add docker and nvidia-container to your default runlevel:

root # rc-update add docker default
 * service docker added to runlevel default
root # rc-update add nvidia-container default
 * nvidia-container added to runlevel default.
root # rc

User Setup

When using docker, you will be starting the Steam container as a regular user account so the container can inherit the connection to your X server. You will want to make sure your user account is in the docker group:

root # gpasswd -a drobbins docker
Adding user drobbins to group docker

You will need to log out and log back in for this group change to take effect.

PulseAudio Setup

In order to allow the container to connect to PulseAudio, you will of course need to be using PulseAudio, and then you will also need to enable support for UNIX socket connectivity in PulseAudio. This can be done by adding the following to /etc/pulse/default.pa:

   /etc/pulse/default.pa
load-module module-native-protocol-unix auth-anonymous=1

Once this is done, you should restart your user's pulseaudio daemon for this to take immediate effect:

user $ killall pulseaudio

Once this has been done, you should be able to see a native UNIX socket in the PulseAudio run directory. This socket will get mapped into the container:

user $ ls /run/user/$UID/pulse/
native   pid