linuxserver/steam pulls statistics

The LinuxServer.io team brings you another container release featuring:

• regular and timely application updates • easy user mappings (PGID, PUID) • custom base image with s6 overlay • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth • regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more! • Discord - realtime support / chat with the community and the team. • Discussions - post on our community forum. • GitHub - view the source for all of our repositories. • Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/steam

Steam is the ultimate destination for playing, discussing, and creating games.

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/steam:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

| Architecture | Available | Tag |

| x86-64 | ✅ | amd64-\ | | arm64 | ❌ | |

Application Setup

The application can be accessed at:

• https://yourhost:3001/

[!NOTE] This image is for a web accessible version of Steam to be played through a web browser, if you want a fully flushed out Moonlight couch solution please consider Wolf or another non Docker solution. Moonlight clients have major advantages over using a web browser specifically for gaming.

Permissions

Steam runs its browser helper and every game inside bubblewrap, which needs user namespaces. Docker's default seccomp profile (and AppArmor on Debian/Ubuntu hosts) blocks those, so the recommended way to run this container is with --security-opt seccomp=unconfined and --security-opt apparmor=unconfined, which lets Steam use bubblewrap as intended.

These options are not required, but running without them will degrade performance as userspace proot with ptrace or fakechroot will be used to run games. proot-bwrap

Gamepad support

This container leverages a userspace gamepad interposer to provide gamepad support. To use a gamepad always force Proton in "Properties>Compatibility" even for Linux native games, "Proton Hotfix" is a good default selection. You cannot use the "Steam Input" feature on any game as the uinput socket and HID do not exist.

Gaming mode

An absolute must for mouse and keyboard input is sending relative mouse input from the browser, you will need to use the "Gaming Mode" which is a small crosshair in the top right of the sidebar. This runs in fullscreen and traps you in the window, to exit this mode hold down escape for 3 seconds.

Game Launching

Included in this image are tools for managing Proton versions and a command line launcher. This means once a game or application is installed via Steam it can be directly launched on init by creating a config file and modifying /config/.config/labwc/autostart to run umu-run instead of Steam.:

This facilitates custom home directories with pre-configured runtimes and gamefiles for baking images outside of using the Steam launcher.

Strict reverse proxies

This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.

This container is based on Docker Baseimage Selkies, which streams a desktop or single application to your web browser. Only the essentials are covered below, the full platform documentation lives at docs.linuxserver.io/selkies.

Start Minimal

Most support issues we see stem from large run configurations assembled from years of forum posts. These containers are designed to work with almost nothing. Start with the minimal command below, confirm it works, then add your options (volumes, env vars, GPU flags) one at a time:

Open https://localhost:3001 (note the https) and accept the self signed certificate warning. The trailing bash gives you a shell inside the container, ctrl+d exits and cleans everything up. If a bigger setup misbehaves, return to this command to isolate the problem, see the Quickstart and Troubleshooting guides.

GPU Acceleration

A GPU is optional, the CPU pipeline is fast enough for smooth sessions on modest hardware. When a GPU is mounted into the container it is automatically detected and configured for zero copy rendering and encoding, set AUTO_GPU=false to disable this behavior.

Intel / AMD (open source drivers), one flag is all it takes:

Nvidia (proprietary drivers, not available on Alpine based images):

Requires host driver 580 or newer installed from the .run file downloaded directly from Nvidia. On drivers older than 595.80 you may also need kernel parameters and a dummy plug, see GPU Acceleration before opening an issue.

Compose examples, multi GPU selection (DRINODE/DRI_NODE), Unraid notes, and a step by step debugging loop are in the GPU Acceleration guide.

Security

[!WARNING] This container provides privileged access to the host system. Do not expose it to the Internet unless you have secured it properly.

HTTPS is required. Modern browser features used for video and audio (WebCodecs) only work in a secure context. Port 3001 serves HTTPS directly, the HTTP port exists only to sit behind a reverse proxy.

By default there is no authentication. Setting the CUSTOM_USER and PASSWORD environment variables enables HTTP basic auth, which is suitable only for a trusted local network. For internet exposure, place the container behind a reverse proxy with robust authentication, such as SWAG. Keep in mind the web interface includes a terminal with passwordless sudo, anyone who can reach the GUI can gain root inside the container.…

Description from the Docker Hub listing.