hectorm/docker-steam

A Docker image for Steam based on Xubuntu on Docker.

docker-steam's Issues

Controller issues with steam link app & remote play

Currently only able to test this with a steam controller.
When using remote play or steam link app the controller fails to work properly in most games.
Using the controller as a mouse works fine, but as soon as the game launches it fails to properly detect a controller in game settings.
List of things that failed to work:

• Adding uinput into docker container via --device /dev/uinput/:/dev/uinput

  • Following these two instructions to get read and write working for uinput:
    https://steamcommunity.com/app/221410/discussions/0/523897277912430760/
    https://steamcommunity.com/app/353370/discussions/2/1735465524711324558/?ctp=35
    Controller shows up as Microsoft X-Box 360 pad (cat /proc/bus/input/devices and dmesg)

  • Installing steam-devices (everything below ran without steam-devices installed)

  • Disabled and enabled steam input & steam overlay

  • Installed sc-controller

• Add --privileged to docker container without uinput read and write
  Controller did not show up in cat /proc/bus/input/devices and dmesg

  • Allow read and write for uinput via chmod +666 /dev/uinput
    Controller shows up as Microsoft X-Box 360 pad (cat /proc/bus/input/devices and dmesg)
    According to Session Stats steam is recognizing it as a steam controller.

In most cases steam shows that a gamepad configuration is being used when the game is running, but nothing on the controller will work.

RemotePlay on SteamLink(Android) do not recognize the gamepad while in game

First of all, thank you for this great approach to steam in docker. Works great for running on Windows RDP (do not know how to use a gamepad over RDP though).

When I try to use it over SteamLink( on Android) I cannot get the gamepad to be recognized once the game starts.

I run the docker-compose in Ubuntu 22.04 VM on Proxmox 7.2 with only three changes.

1 added in devices: - '/dev/uinput:/dev/uinput' (As I found in other issue rised here that was the solution)
2 added in security_opt: - 'apparmor=unconfined' (For proton to work)
3 added volumes: - '/media:/media' (For storing the games)

Is there something else I need to do for the controller to be recognized while in the games ? I'm testing with brawhalla currently.

Another question, what is the best approach for setting the container to start steam automatically on each boot?

Proton 5.13 and up fail

When testing steam games proton doesn't work for anything 5.13 and up.
Not sure if anyone else has this issue.
I know that proton 5.13 and up uses steam runtime soldier and it is know to cause issues.
Tried variety of games known to work with 5.13 or greater. All games refuse to open.

Tried proton logs, but they don't give any output. Also uninstalled steam and installed it from apt.
Tried installing proton-ge with same result.
Only thing that kind of works was using proton-caller