[Support] Josh5 - Steam (Headless)


Recommended Posts

So what I ended up doing was just reinstalling Steam-Headless entirely and everything now works. My mistake was, as you had suggested to someone else earlier, that I installed steam-headless before installing uinput. To save you some headaches Josh I would reccomend you make it clear in big bold letters at the top that all users should install uinput before installing steam-headless. I would think that doing so will save you and users some headaches as im sure most people will be using controllers.
 
While I read your stuff regarding uinput, in my naevity I didn't think it was necessary for remote play controllers to work. I suspect most users will want to play using controllers so insisting on users installing uinput FIRST will likely prevent unnecessary support.
 
also assuming once an arch-based steamos 3.0 version exists in the future, if you aren't aware of it already, I would like to suggest an additional script to install chimera, which allows you to install heroic epic games, and retroarch games directly to steam big picture mode for convenience via web on your local network. steam-headless seems like a perfect situation where chimera would be useful. dont think there's a way to install on debian but im no linux master. chimera 
Glad to hear you have it working. I'll update some of the docs with your suggestions. Thanks.

I've got an arch base build ready. It just really sucks. Because of the way that the packages work for steam and Nvidia, it requires a lot of bloat. This debian release sits at around 2GB for the docker image, the arch one pushed that closer to 3 for no reason other than the arch package repos not being a good fit for docker images.
I also ran into some really weird input issues that I have not solved yet. Keyboard input would not work with steam in arch, but it worked in every other app or in steam big picture. I could not figure out what I was missing.
Flatpaks are possibly a solution for running things inside the arch container, but the flatpak for steam had the same kind of issues that you have with the controller, as well as some audio issues and the fact that paths are messed up and not easily shared outside of steam.
I'm really on the fence now as I totally wanted to keep this inline with SteamOS 3 when it was released, but now I can't see a benefit to doing so. I've put a pin in that arch docker image for the next few months until we see SteamOS 3 released.
Link to comment

After a fresh install.

 

Removed plugin, removed container. Full reboot, reinstall plugin, reboot, reinstall container. It appears to be working with my limited testing. (test from phone using touch controller, and pc using steam streaming)

 

I believe my issue was the template I had was missing a few parameters, after reviewing the advanced settings. Notably the "-v '/dev/input':'/dev/input':'ro'" which makes way more sense now to why it was not working.

 

The only thing I'm noticing is that I get latency spikes every now and then. I need more time to mess around with it more.


Also it seems to be limited to outputting 1080P at most. I believe I have a 4k Dongle attached to the gpu via hdmi, but maybe its using the iGPU monitor to detect resolutions?

 

The iGPU has a monitor connected that is limited to 1080P. But unraid is not booted into GUI mode, just regular terminal mode.

Edited by randomninjaatk
Link to comment

If anyone is running this container with an AMD GPU, could you let us know what was required to get it working.

I'm guessing:

  1. Radeon-TOP plugin installed
  2. NVIDIA `--runtime=nvidia` removed from extra params

Was there any other steps required?

 

Can everyone see /dev/dri/* without needing to pass that through to the container? I am assuming so if they are able to use VAAPI for encoding with steam.

 

Link to comment
18 hours ago, Josh.5 said:

If anyone is running this container with an AMD GPU, could you let us know what was required to get it working.

I'm guessing:

  1. Radeon-TOP plugin installed
  2. NVIDIA `--runtime=nvidia` removed from extra params

Was there any other steps required?

 

Can everyone see /dev/dri/* without needing to pass that through to the container? I am assuming so if they are able to use VAAPI for encoding with steam.

 

1.Yes

2.Yes

 

thats it.

Link to comment

Trying to get this one up and running with my AMD APU, But its not starting up. Im using network:host and the only ports that are mapped in the template are 8083, 32123, 2222 which are all not used in the existing docker allocations.

 

I removed the --runtime=nvidia from the extra params. The other nvidia variables i had to leave in otherwise the container wouldnt install at all (screenshot)

 

Here is my docker log:

 

**** Configure default user ****
Setting run user uid=100(default) gid=99(default)
usermod: no changes
Adding run user to video, input and audio groups
Setting umask to 000
Create the user XDG_RUNTIME_DIR path '/run/user/99'
Adding default home directory template
Setting root password
Setting user password
DONE

[ /etc/cont-init.d/20-configre_sshd.sh: executing... ]
**** Configure SSH service ****
DONE

[ /etc/cont-init.d/30-configure_dbus.sh: executing... ]
**** Configure container dbus ****
Container configured to run its own dbus
DONE

[ /etc/cont-init.d/30-configure_udev.sh: executing... ]
**** Configure container to run udev management ****
**** Ensure the default user has the correct permissions on input devices ****
Adding user 'default' to groups: user-gid-71

[ /etc/cont-init.d/40-setup_locale.sh: executing... ]
**** Locales already set correctly to en_US.UTF-8 UTF-8 ****
DONE

[ /etc/cont-init.d/50-configure_vnc_audio.sh: executing... ]
**** Configure VNC audio ****
Configure pulseaudio to pipe audio to a socket
DONE

[ /etc/cont-init.d/80-configure_gpu_driver.sh: executing... ]
/etc/cont-init.d/80-configure_gpu_driver.sh: line 16: nvidia-smi: command not found
**** No NVIDIA device found ****
DONE

[ /etc/cont-init.d/90-configure_xorg.sh: executing... ]
**** Generate default xorg.conf ****
Configure container as primary the X server
DONE

**** Starting supervisord ****
Logging all root services to '/var/log/supervisor/'
Logging all user services to '/home/default/.cache/log/'

2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/dbus.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/desktop.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/pulseaudio.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/sshd.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/steam.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/udev.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/vnc-audio.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/vnc.ini" during parsing
2022-02-03 09:05:32,556 INFO Included extra file "/etc/supervisor.d/xorg.ini" during parsing
2022-02-03 09:05:32,556 INFO Set uid to user 0 succeeded
Error: Another program is already listening on a port that one of our HTTP servers is configured to use. Shut this program down first before starting supervisord.

For help, use /usr/bin/supervisord -h

 

image.thumb.png.486e01f95b89b26820ff8a864930f1ec.png

 

 

After stopping all other containers i got further through the logs, but still not starting up. when starting the webUI the VNC wont connect. EDIT: running all containers again, my MQTT container was not starting until i stopped the steam container. the MQTT container is using ports 1883 and 9001

 

[ /etc/cont-init.d/90-configure_xorg.sh: executing... ]
**** Generate default xorg.conf ****
Configure container as primary the X server
DONE

**** Starting supervisord ****
Logging all root services to '/var/log/supervisor/'
Logging all user services to '/home/default/.cache/log/'

2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/dbus.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/desktop.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/pulseaudio.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/sshd.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/steam.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/udev.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/vnc-audio.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/vnc.ini" during parsing
2022-02-03 10:20:05,460 INFO Included extra file "/etc/supervisor.d/xorg.ini" during parsing
2022-02-03 10:20:05,460 INFO Set uid to user 0 succeeded
2022-02-03 10:20:05,467 INFO RPC interface 'supervisor' initialized
2022-02-03 10:20:05,468 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Unlinking stale socket /run/supervisor.sock
2022-02-03 10:20:05,770 INFO RPC interface 'supervisor' initialized
2022-02-03 10:20:05,770 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-02-03 10:20:05,771 INFO supervisord started with pid 1
2022-02-03 10:20:06,774 INFO spawned: 'audiostream' with pid 144
2022-02-03 10:20:06,776 INFO spawned: 'audiowebsock' with pid 145
2022-02-03 10:20:06,777 INFO spawned: 'dbus' with pid 146
2022-02-03 10:20:06,778 INFO spawned: 'pulseaudio' with pid 147
2022-02-03 10:20:06,780 INFO spawned: 'sshd' with pid 148
2022-02-03 10:20:06,781 INFO spawned: 'udev' with pid 149
2022-02-03 10:20:06,783 INFO spawned: 'xorg' with pid 150
2022-02-03 10:20:06,785 INFO spawned: 'novnc' with pid 151
2022-02-03 10:20:06,787 INFO spawned: 'x11vnc' with pid 152
2022-02-03 10:20:06,791 INFO spawned: 'desktop' with pid 155
2022-02-03 10:20:06,792 INFO exited: audiostream (exit status 111; not expected)
2022-02-03 10:20:07,814 INFO spawned: 'audiostream' with pid 271
2022-02-03 10:20:07,815 INFO success: audiowebsock entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,815 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,816 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-02-03 10:20:07,823 INFO exited: audiostream (exit status 111; not expected)
2022-02-03 10:20:10,014 INFO spawned: 'audiostream' with pid 280
2022-02-03 10:20:10,019 INFO exited: audiostream (exit status 111; not expected)
2022-02-03 10:20:10,019 INFO reaped unknown pid 278 (exit status 0)
2022-02-03 10:20:10,581 INFO reaped unknown pid 340 (exit status 1)
2022-02-03 10:20:13,614 INFO spawned: 'audiostream' with pid 496
2022-02-03 10:20:13,622 INFO exited: audiostream (exit status 111; not expected)
2022-02-03 10:20:13,623 INFO gave up: audiostream entered FATAL state, too many start retries too quickly

 

 

Last edit I promise. Took a while to come up (Had to shut down the MQTT container for it to work), but i can now connect via the webUI, but it is painfully slow. and I get this in the middle of the image: image.png.2c88d4dd66001a7895470964df8c2c18.png

Edited by eatoff
Link to comment
On 2/2/2022 at 12:21 PM, Josh.5 said:

Can everyone see /dev/dri/* without needing to pass that through to the container? I am assuming so if they are able to use VAAPI for encoding with steam.

What's the easiest way to check this?

 

EDIT: yes its listed when i checked via the console in the container. But the performance I'm getting is terrible. Very laggy, and only using ~5% GPU according to radeontop. VNC is very slow too. I'm running 6.10RC2. I had to change network to br0 to avoid conflict with my other containers... but then it seems the controller isnt working (the onscreen controller when streaming to phone).

Edited by eatoff
Link to comment
On 2/3/2022 at 7:18 AM, domrockt said:

1.Yes

2.Yes

 

thats it.

Edit: NVM, full server reboot and it's working. Apart from controller support, that's not working, but that's because I'm not using host network due to port conflicts

Edited by eatoff
Link to comment
On 2/3/2022 at 2:09 AM, eatoff said:

 

Last edit I promise. Took a while to come up (Had to shut down the MQTT container for it to work), but i can now connect via the webUI, but it is painfully slow. and I get this in the middle of the image: image.png.2c88d4dd66001a7895470964df8c2c18.png

 

 

i can help you with that, it just means that your browser cant be used as a source, i use firefox for that noVNC window

Link to comment
On 2/4/2022 at 6:05 AM, sonic_reaction said:

Is it possible to run this if you don't have a GPU attached? I just want a steam client to run to just update games and nothing else.

The latest build has the ability to be run in a simple framebuffer.

To enable this, update the Mode to say "framebuffer". Obviously this mode will be useless for playing games, but it will work fine for downloading and updating games.

Make sure you pull the latest docker image.
image.thumb.png.d5e3c73544d9d8a034fb993336501d4d.png

  • Like 1
Link to comment

I've made a second template for this docker image.

 

This Docker image has a few little init scripts that can configure it in different ways (Intel iGPU, APD GPU, NVIDIA GPU, X Server, no X server, VNC Audio mod, etc...). One of these config sets I have dubbed "secondary mode" where it basically just runs the steam client. This is useful when you already have an X server running somewhere else.

 

Up until this past weekend I had no use for secondary mode, so I had not put any real effort into it. But then I wanted to play a game with my wife and for her to use Steam Link I had to go to my PC first, log into the Web VNC portal, sign out of my profile, sign into hers. And then when we were done I had to reverse it. And that was just annoying.

Steam Link has not capability to switch profiles when it connects and this is a feature I really want!

 

To solve this issue I created a "Steam Headless Secondary" template which I share with you today in CA.

What this template does:

  • Allow you to run multiple instances of steam logged into different accounts.
  • Run a second instance of steam in the same desktop as an existing Steam Headless.
  • Run a second instance of steam in an existing desktop environment. Eg. booted Unraid in GUI mode (Untested).
  • Uses the exact same Docker image as Steam Headless so no additional disk space is used when you run this second instance.
  • Supports controllers and NVIDIA/AMD GPU just the same as Steam Headless.

What this template does not do:

  • Allow you to play two games at a time (We are limited by X11).
Link to comment
1 hour ago, Josh.5 said:

Supports controllers and NVIDIA/AMD GPU just the same as Steam Headless

How can we get controller support for instances where we can't use network: host

 

If you're running 2 instances then you can't be using host network for both to get controller support for both at the same time yeah?

 

I think that's all I'm missing, I need to be able to use a controller with a custom network address due to the number of other containers I'm already running

Edited by eatoff
Clarification
Link to comment
14 minutes ago, eatoff said:

How can we get controller support for instances where we can't use network: host

 

If you're running 2 instances then you can't be using host network for both to get controller support for both at the same time yeah?

 

I think that's all I'm missing, I need to be able to use a controller with a custom network address due to the number of other containers I'm already running

The secondary container does not use host network. 

 

Why can you not start the main Steam Headless container with net=host? What errors do you get in the logs when you try?

Link to comment
31 minutes ago, Josh.5 said:

The secondary container does not use host network. 

 

Why can you not start the main Steam Headless container with net=host? What errors do you get in the logs when you try?

Ok, so i just tried again and it came u fine. I updated it to the latest version.

 

The problems i was experiencing before was this - 

 

My problem now is that my xbox controller doesnt work. Its paired to my google TV via bluetooth. My phone with on screen controls doesnt work either. My PC running keyboard and mouse streams just fine. Running 6.10RC2, the plugin is installed too. Server has been rebooted with no effect

Edited by eatoff
Link to comment
Pulling image: josh5/steam-headless:develop

TOTAL DATA PULLED: 0 B
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='steam-headless-secondary' --net='steam' --ip='192.168.1.147' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="SERVER" -e HOST_CONTAINERNAME="steam-headless-secondary" -e 'USER_PASSWORD'='PASSWORD' -e 'TZ'='Europe/London' -e 'USER_LOCALES'='en_US.UTF-8 UTF-8' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':55' -e 'MODE'='secondary' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/user/appdata/steam-headless-secondary':'/home/default':'rw' -v '/mnt/user/Games':'/mnt/games':'rw' --hostname='SteamHeadlessSecondary' --add-host='SteamHeadlessSecondary:127.0.0.1' --restart=unless-stopped --shm-size=2G -v '/tmp/.X11-unix':'/tmp/.X11-unix':'rw' -v '/dev/input':'/dev/input':'ro' 'josh5/steam-headless:develop'
Unable to find image 'josh5/steam-headless:develop' locally
docker: Error response from daemon: manifest for josh5/steam-headless:develop not found: manifest unknown: manifest unknown.
See 'docker run --help'.

The command failed.

 

Getting this error when trying to install. 😕

 

Link to comment
Pulling image: josh5/steam-headless:developTOTAL DATA PULLED: 0 B

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='steam-headless-secondary' --net='steam' --ip='192.168.1.147' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="SERVER" -e HOST_CONTAINERNAME="steam-headless-secondary" -e 'USER_PASSWORD'='PASSWORD' -e 'TZ'='Europe/London' -e 'USER_LOCALES'='en_US.UTF-8 UTF-8' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':55' -e 'MODE'='secondary' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/user/appdata/steam-headless-secondary':'/home/default':'rw' -v '/mnt/user/Games':'/mnt/games':'rw' --hostname='SteamHeadlessSecondary' --add-host='SteamHeadlessSecondary:127.0.0.1' --restart=unless-stopped --shm-size=2G -v '/tmp/.X11-unix':'/tmp/.X11-unix':'rw' -v '/dev/input':'/dev/input':'ro' 'josh5/steam-headless:develop'Unable to find image 'josh5/steam-headless:develop' locallydocker: Error response from daemon: manifest for josh5/steam-headless:develop not found: manifest unknown: manifest unknown.See 'docker run --help'.The command failed.

 
Getting this error when trying to install. 
 

Oops. Change :develop to :latest
I missed that when creating the template
Link to comment

Hey, i have a weird issue. After one of the last updates, the container doesnt start anymore, it keeps looping through this cycle:

Build: [02/08/22 01:36:51] [master] [75c2df31157b4b86e9a712e0d9a866152ffab516]

[ /etc/cont-init.d/10-setup_user.sh: executing... ]
**** Configure default user ****
Setting run user uid=100(default) gid=99(default)
Adding run user to video, input and audio groups
Setting umask to 000
Create the user XDG_RUNTIME_DIR path '/run/user/99'
Adding default home directory template
Setting root password
Setting user password
DONE

[ /etc/cont-init.d/20-configre_sshd.sh: executing... ]
**** Configure SSH service ****
DONE

[ /etc/cont-init.d/30-configure_dbus.sh: executing... ]
**** Configure container dbus ****
Container configured to run its own dbus
DONE

[ /etc/cont-init.d/30-configure_udev.sh: executing... ]
**** Configure container to run udev management ****
**** Ensure the default user has the correct permissions on input devices ****
Allow /dev/uinput r/w to the group
Adding user 'default' to groups: user-gid-71,root

[ /etc/cont-init.d/40-setup_locale.sh: executing... ]
**** Configuring Locales to de_DE.UTF-8 UTF-8 ****
Generating locales (this might take a while)...
de_DE.UTF-8... done
en_US.UTF-8... done
Generation complete.
DONE

[ /etc/cont-init.d/50-configure_pulseaudio.sh: executing... ]
**** Configure pulseaudio ****
Configure pulseaudio to pipe audio to a socket
DONE

[ /etc/cont-init.d/70-configure_vnc_audio.sh: executing... ]
**** Configure VNC audio ****
Disable audio stream
Disable audio websock
DONE

[ /etc/cont-init.d/80-configure_gpu_driver.sh: executing... ]
**** Found NVIDIA device 'NVIDIA T600' ****
Downloading driver v510.39.01



and that over and over again. Any ideas?

Link to comment
Hey, i have a weird issue. After one of the last updates, the container doesnt start anymore, it keeps looping through this cycle:

Build: [02/08/22 01:36:51] [master] [75c2df31157b4b86e9a712e0d9a866152ffab516]

[ /etc/cont-init.d/10-setup_user.sh: executing... ]
**** Configure default user ****
Setting run user uid=100(default) gid=99(default)
Adding run user to video, input and audio groups
Setting umask to 000
Create the user XDG_RUNTIME_DIR path '/run/user/99'
Adding default home directory template
Setting root password
Setting user password
DONE

[ /etc/cont-init.d/20-configre_sshd.sh: executing... ]
**** Configure SSH service ****
DONE

[ /etc/cont-init.d/30-configure_dbus.sh: executing... ]
**** Configure container dbus ****
Container configured to run its own dbus
DONE

[ /etc/cont-init.d/30-configure_udev.sh: executing... ]
**** Configure container to run udev management ****
**** Ensure the default user has the correct permissions on input devices ****
Allow /dev/uinput r/w to the group
Adding user 'default' to groups: user-gid-71,root

[ /etc/cont-init.d/40-setup_locale.sh: executing... ]
**** Configuring Locales to de_DE.UTF-8 UTF-8 ****
Generating locales (this might take a while)...
de_DE.UTF-8... done
en_US.UTF-8... done
Generation complete.
DONE

[ /etc/cont-init.d/50-configure_pulseaudio.sh: executing... ]
**** Configure pulseaudio ****
Configure pulseaudio to pipe audio to a socket
DONE

[ /etc/cont-init.d/70-configure_vnc_audio.sh: executing... ]
**** Configure VNC audio ****
Disable audio stream
Disable audio websock
DONE

[ /etc/cont-init.d/80-configure_gpu_driver.sh: executing... ]
**** Found NVIDIA device 'NVIDIA T600' ****
Downloading driver v510.39.01



and that over and over again. Any ideas?
Perhaps it is failing to download or install the driver
Link to comment

HDMI dummy plug solved all my issues. VNC is now responsive, and controller support works. Pretty good performance, very impressed.

 

I did run into an issue though, I ran the docker safe permissions to fix some permission issues, and then couldn't launch any games.

 

Had to manually change the permissions in my games folder. Is there a way to get the permissions working without changing them back. I run that new permissions script more often than I'd care to admit

Link to comment
HDMI dummy plug solved all my issues. VNC is now responsive, and controller support works. Pretty good performance, very impressed.
 
I did run into an issue though, I ran the docker safe permissions to fix some permission issues, and then couldn't launch any games.
 
Had to manually change the permissions in my games folder. Is there a way to get the permissions working without changing them back. I run that new permissions script more often than I'd care to admit
I do not recommend using the docker safe permissions script on your games library.
Link to comment
On 2/1/2022 at 12:52 PM, Josh.5 said:

Glad to hear you have it working. I'll update some of the docs with your suggestions. Thanks.

I've got an arch base build ready. It just really sucks. Because of the way that the packages work for steam and Nvidia, it requires a lot of bloat. This debian release sits at around 2GB for the docker image, the arch one pushed that closer to 3 for no reason other than the arch package repos not being a good fit for docker images.
I also ran into some really weird input issues that I have not solved yet. Keyboard input would not work with steam in arch, but it worked in every other app or in steam big picture. I could not figure out what I was missing.
Flatpaks are possibly a solution for running things inside the arch container, but the flatpak for steam had the same kind of issues that you have with the controller, as well as some audio issues and the fact that paths are messed up and not easily shared outside of steam.
I'm really on the fence now as I totally wanted to keep this inline with SteamOS 3 when it was released, but now I can't see a benefit to doing so. I've put a pin in that arch docker image for the next few months until we see SteamOS 3 released.

Yeah I tried ChimeraOS first before your docker image and it was just a mess, nevermind that ChimeraOS doesn't install a desktop which is kind of necessary to use stuff like Lutris easily. Hopefully SteamOS3 will be at least managable to port to a new container once it's released. I would assume it's just KDE + a steamos session with gamescope/steam compositor but we'll see I guess. 

  • Like 1
Link to comment

Great container!


Got it working without to much hassle but one strange thing that I can't seem to find a solution for. When trying to access noVNC I instead see my VM's console window. If I shutdown the VM I can access steam-headless instead.


What could be the cause for this? I looked trough the thread but couldn't find any similar problems or I missed it.

Link to comment
Great container!

Got it working without to much hassle but one strange thing that I can't seem to find a solution for. When trying to access noVNC I instead see my VM's console window. If I shutdown the VM I can access steam-headless instead.

What could be the cause for this? I looked trough the thread but couldn't find any similar problems or I missed it.
What do the logs say?

Possibly a port conflict with port 8083
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.