Skip to content
Jo Colina edited this page Jun 18, 2025 · 7 revisions

banner

What is Plasma?

Plasma is a spiritual fork of docker-steam-headless.

Plasma is a small system for self-hosting remote gaming (think Shadow.tech, Nvidia GeForce Now, Amazon Luna...). It achieves this by packaging everything you need in a Docker image.

It is not meant to work out-of-the-box (although it could), and requires some tinkering. Once you've built your Plasma image, it should be able to run repeatedly if the container restarts.

Who is Plasma for?

Plasma is meant for tinkerers and tech-savvy individuals. The way Plasma is built, configured and installed requires some IT knowledge that computer science engineers and home-labbers will probably have.

Plasma also requires you to have a system where you can run containers (ie: with docker or kubernetes). This is usually a home-lab or server, usually on for 24h-7-days a week. If these words mean nothing to you, you can look for ready-to-use solutions, or allow us to welcome you to the big-wide-world of container deployments (you'll need ~1 day for "quick" setup, or ~1week to learn).

If you're looking for a ready-to-use solution, we can recommend some other platforms

Philosophy

Immutability

We aim to make Plasma as immutable as possible. This means that you can

  • build Plasma once, run it indefinitely

We do this by packaging as much as possible in the Docker image itself, including some settings (like Sunshine credentials, Xorg configuration) and the graphic drivers.

This means that if your server reboots for any reason, or the container needs to be re-created, Plasma will reduce the chances of new libraries, packages or drivers being installed, thus reducing incompatibility problems.

Note

A big exception is Steam. Although we pre-install Steam in the image, it auto-updates when first booting.

Using volumes will prevent Steam from re-installing every time the container restarts

Ease of use

Plasma is also made to be easy to setup and install.

Setting Plasma up should be well documented and easy to do, via environment variables or configuration files in container volumes.

We also provide the building steps as a GitHub action. It is meant to be easy to use and trigger. Please refer to the GitHub Action instructions

Ready-to-use platforms

Only gaming:

Full desktop:

Compatibility table

Arch

Architecture Compatible Tested
x86 / amd64 Yes
arm ? No

GPU

Brand Compatible Tested Comments
NVIDIA 🟡 Yes Tested on a NVIDIA Quadro P400. Only tested as far as getting input and display. Also tested KSP. Should work with Steam in Big Picture mode
AMD Yes Tested entirely on an AMD Radeon Pro WX 2100, ran KSP and Factorio linux distributions. Ran RCT2 via Proton
Intel ? No
Clone this wiki locally