Mrtj18 Posted October 4, 2023 Share Posted October 4, 2023 (edited) Quick question, has anyone gotten csgo 2 to run in this docker? No matter which proton version I select the game fails to launch. Nevermind user error edit - I didn't have the Nvidia flag in the extra paremintars set. So games was launching without finding the GPU I had selected. Edited October 6, 2023 by Mrtj18 Update Quote Link to comment
MarianKoniuszko Posted October 15, 2023 Share Posted October 15, 2023 Hello, @Josh.5 I buy new Nvidia GPU and add to my server. I have also intel integrated GPU with i5-12600K. I install steam-headless one more time and add extra parameter: --runtime='nvidia' at the beginning. I go to webgui and click connect but have error at top of site. Logs shows me: 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/dbus.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/desktop.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/neko.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/pulseaudio.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/steam.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/sunshine.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/udev.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/vnc-audio.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/vnc.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/wol-power-manager.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/xorg.ini" during parsing 2023-10-15 10:26:38,033 INFO Included extra file "/etc/supervisor.d/xvfb.ini" during parsing 2023-10-15 10:26:38,033 INFO Set uid to user 0 succeeded 2023-10-15 10:26:38,035 INFO RPC interface 'supervisor' initialized 2023-10-15 10:26:38,035 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2023-10-15 10:26:38,035 INFO supervisord started with pid 1 2023-10-15 10:26:39,036 INFO spawned: 'dbus' with pid 980 2023-10-15 10:26:39,037 INFO spawned: 'udev' with pid 981 2023-10-15 10:26:39,038 INFO spawned: 'xorg' with pid 982 2023-10-15 10:26:39,039 INFO spawned: 'frontend' with pid 983 2023-10-15 10:26:39,040 INFO spawned: 'pulseaudio' with pid 985 2023-10-15 10:26:39,041 INFO spawned: 'x11vnc' with pid 988 2023-10-15 10:26:39,043 INFO spawned: 'desktop' with pid 991 2023-10-15 10:26:39,044 INFO spawned: 'sunshine' with pid 997 PULSEAUDIO: Starting pulseaudio service 2023-10-15 10:26:39,052 INFO reaped unknown pid 1009 (exit status 0) 2023-10-15 10:26:39,090 WARN exited: udev (exit status 1; not expected) 2023-10-15 10:26:40,063 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,063 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,063 INFO success: frontend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,063 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,064 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,064 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,064 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:40,124 INFO spawned: 'udev' with pid 1047 2023-10-15 10:26:40,170 WARN exited: udev (exit status 1; not expected) 2023-10-15 10:26:43,069 INFO spawned: 'udev' with pid 1092 2023-10-15 10:26:43,115 WARN exited: udev (exit status 1; not expected) 2023-10-15 10:26:47,069 INFO spawned: 'udev' with pid 1140 2023-10-15 10:26:47,116 WARN exited: udev (exit status 1; not expected) 2023-10-15 10:26:48,117 INFO gave up: udev entered FATAL state, too many start retries too quickly 2023-10-15 10:26:49,051 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:26:49,052 INFO spawned: 'xorg' with pid 1167 2023-10-15 10:26:50,054 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:26:59,066 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:26:59,067 INFO spawned: 'xorg' with pid 1300 2023-10-15 10:27:00,069 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:09,081 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:27:09,083 INFO spawned: 'xorg' with pid 1433 2023-10-15 10:27:09,178 WARN exited: x11vnc (exit status 11; not expected) 2023-10-15 10:27:09,178 WARN exited: desktop (exit status 11; not expected) 2023-10-15 10:27:09,178 WARN exited: sunshine (exit status 11; not expected) 2023-10-15 10:27:09,180 INFO spawned: 'x11vnc' with pid 1437 2023-10-15 10:27:09,181 INFO spawned: 'desktop' with pid 1438 2023-10-15 10:27:09,182 INFO spawned: 'sunshine' with pid 1439 2023-10-15 10:27:10,187 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:10,187 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:10,187 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:10,187 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:10,187 INFO reaped unknown pid 1450 (exit status 0) 2023-10-15 10:27:19,096 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:27:19,098 INFO spawned: 'xorg' with pid 1579 2023-10-15 10:27:20,099 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:29,112 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:27:29,114 INFO spawned: 'xorg' with pid 1715 2023-10-15 10:27:30,115 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:39,128 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:27:39,130 INFO spawned: 'xorg' with pid 1849 2023-10-15 10:27:39,326 WARN exited: x11vnc (exit status 11; not expected) 2023-10-15 10:27:39,326 WARN exited: desktop (exit status 11; not expected) 2023-10-15 10:27:39,326 WARN exited: sunshine (exit status 11; not expected) 2023-10-15 10:27:39,328 INFO spawned: 'x11vnc' with pid 1853 2023-10-15 10:27:39,329 INFO spawned: 'desktop' with pid 1854 2023-10-15 10:27:39,329 INFO spawned: 'sunshine' with pid 1855 2023-10-15 10:27:40,334 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:40,335 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:40,335 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:40,335 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:40,335 INFO reaped unknown pid 1866 (exit status 0) 2023-10-15 10:27:49,144 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:27:49,145 INFO spawned: 'xorg' with pid 1995 2023-10-15 10:27:50,147 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:27:59,159 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:27:59,161 INFO spawned: 'xorg' with pid 2128 2023-10-15 10:28:00,161 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:28:09,174 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:28:09,175 INFO spawned: 'xorg' with pid 2261 2023-10-15 10:28:09,465 WARN exited: x11vnc (exit status 11; not expected) 2023-10-15 10:28:09,465 WARN exited: desktop (exit status 11; not expected) 2023-10-15 10:28:09,465 WARN exited: sunshine (exit status 11; not expected) 2023-10-15 10:28:09,466 INFO spawned: 'x11vnc' with pid 2265 2023-10-15 10:28:09,467 INFO spawned: 'desktop' with pid 2266 2023-10-15 10:28:09,468 INFO spawned: 'sunshine' with pid 2267 2023-10-15 10:28:10,473 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:28:10,473 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:28:10,473 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:28:10,473 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:28:10,473 INFO reaped unknown pid 2278 (exit status 0) 2023-10-15 10:28:19,189 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:28:19,191 INFO spawned: 'xorg' with pid 2407 2023-10-15 10:28:20,191 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-10-15 10:28:29,204 WARN exited: xorg (exit status 11; not expected) 2023-10-15 10:28:29,206 INFO spawned: 'xorg' with pid 2540 2023-10-15 10:28:30,207 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Quote Link to comment
Josh.5 Posted October 15, 2023 Author Share Posted October 15, 2023 @MarianKoniuszkopost your docker run command. Looks symptomatic of you mounting /run/udev or /dev/input Quote Link to comment
MarianKoniuszko Posted October 15, 2023 Share Posted October 15, 2023 10 minutes ago, Josh.5 said: @MarianKoniuszkopost your docker run command. Looks symptomatic of you mounting /run/udev or /dev/input Hi, I forget to mention I connect new nvidia card to my tv with hdmi-DisplayPort cable. I don't have any dumy plug for my igpu (meybe I should try? Because my VAAPI transcoding is gone in Emby now). docker run -d --name='steam-headless' --net='host' -e TZ="Europe/Warsaw" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRAID" -e HOST_CONTAINERNAME="steam-headless" -e 'USER_PASSWORD'='mypassword' -e 'TZ'='Europe/Warsaw' -e 'USER_LOCALES'='en_US.UTF-8 UTF-8' -e 'WEB_UI_MODE'='vnc' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':55' -e 'MODE'='primary' -e 'PORT_NOVNC_WEB'='8083' -e 'ENABLE_VNC_AUDIO'='false' -e 'ENABLE_EVDEV_INPUTS'='false' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8083]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/user/appdata/steam-headless':'/home/default':'rw' -v '/mnt/user/GRY/':'/mnt/games':'rw' --runtime='nvidia' --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart='unless-stopped' --shm-size='2G' --ipc='host' -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' -v '/dev/input/':'/dev/input/':'ro' -v '/run/udev/data/':'/run/udev/data/':'ro' -v 'steam-headless-var-lib-flatpak':'/var/lib/flatpak/':'rw' --ulimit='nofile=1024:524288' --device='/dev/fuse' --device='/dev/uinput' --device-cgroup-rule='c 13:* rmw' --cap-add='NET_ADMIN' --cap-add='SYS_ADMIN' --cap-add='SYS_NICE' --security-opt='seccomp=unconfined' 'josh5/steam-headless:latest' ed9521f2d2.... The command finished successfully! Quote Link to comment
MarianKoniuszko Posted October 15, 2023 Share Posted October 15, 2023 (edited) @Josh.5 do I have to enable VM in unRAID? Or meybe `Display ID: :55` option should be changed? I have my nvidia GPU connected to TV with hdmi-displayport cable. OK, I change to `:0` and now works. Edited October 15, 2023 by MarianKoniuszko Quote Link to comment
Josh.5 Posted October 15, 2023 Author Share Posted October 15, 2023 9 hours ago, MarianKoniuszko said: Hi, I forget to mention I connect new nvidia card to my tv with hdmi-DisplayPort cable. I don't have any dumy plug for my igpu (meybe I should try? Because my VAAPI transcoding is gone in Emby now). docker run -d --name='steam-headless' --net='host' -e TZ="Europe/Warsaw" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRAID" -e HOST_CONTAINERNAME="steam-headless" -e 'USER_PASSWORD'='mypassword' -e 'TZ'='Europe/Warsaw' -e 'USER_LOCALES'='en_US.UTF-8 UTF-8' -e 'WEB_UI_MODE'='vnc' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':55' -e 'MODE'='primary' -e 'PORT_NOVNC_WEB'='8083' -e 'ENABLE_VNC_AUDIO'='false' -e 'ENABLE_EVDEV_INPUTS'='false' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8083]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/user/appdata/steam-headless':'/home/default':'rw' -v '/mnt/user/GRY/':'/mnt/games':'rw' --runtime='nvidia' --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart='unless-stopped' --shm-size='2G' --ipc='host' -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' -v '/dev/input/':'/dev/input/':'ro' -v '/run/udev/data/':'/run/udev/data/':'ro' -v 'steam-headless-var-lib-flatpak':'/var/lib/flatpak/':'rw' --ulimit='nofile=1024:524288' --device='/dev/fuse' --device='/dev/uinput' --device-cgroup-rule='c 13:* rmw' --cap-add='NET_ADMIN' --cap-add='SYS_ADMIN' --cap-add='SYS_NICE' --security-opt='seccomp=unconfined' 'josh5/steam-headless:latest' ed9521f2d2.... The command finished successfully! It is failing because you have. -v '/dev/input/':'/dev/input/':'ro' -v '/run/udev/data/':'/run/udev/data/':'ro' You have not updated your container template. Quote Link to comment
Josh.5 Posted October 15, 2023 Author Share Posted October 15, 2023 8 hours ago, MarianKoniuszko said: @Josh.5 do I have to enable VM in unRAID? Or meybe `Display ID: :55` option should be changed? I have my nvidia GPU connected to TV with hdmi-displayport cable. OK, I change to `:0` and now works. Have you also booted unraid in gui mode? This would also be wrong. Quote Link to comment
MarianKoniuszko Posted October 15, 2023 Share Posted October 15, 2023 19 minutes ago, Josh.5 said: Have you also booted unraid in gui mode? This would also be wrong. No I don't boot in steamos GUI. I reinstall fresh container few more times (also remove appdata folder) and now cannot make it work properly. I don't know why my screen is smaller and I cannot click icons in top bar. I try extraparameters: --runtime='nvidia' and --runtime=nvidia Quote Link to comment
MarianKoniuszko Posted October 19, 2023 Share Posted October 19, 2023 On 1/15/2022 at 5:50 PM, Josh.5 said: In order to keep the Docker image size below 3GB, I've decided to roll out installer scripts with the image. You can initialise these from the menu under Applications > Games. These installers will generate a installation script that will live in ~/init.d/* and will be executed on container startup. If you update the container image or modify the template settings, the install scripts will re-install the various applications next start of the container. Hello, I don't have that installers in that tab. I have empty folder: `/init.d`. How to install lutris on unraid? Can I install with `sudo apt install lutris`? Will that not broke anything? Because I try flatpak and it don't work properly. Regards. Quote Link to comment
Vyktrii Posted October 21, 2023 Share Posted October 21, 2023 My container runs perfectly fine but i have noticed errors in my unraid log due to the container, should i be worried, can i stop them ? These errors keep on repeating endlessly... Oct 21 11:28:42 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:28:45 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:29:36 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:29:36 Kassandra kernel: traps: light-locker[28607] trap int3 ip:14be754387d7 sp:7ffe12288210 error:0 in libglib-2.0.so.0.7400.6[14be753fa000+8d000] Oct 21 11:29:36 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:29:36 Kassandra kernel: input: Logitech Wireless Mouse PID:4038 as /devices/virtual/input/input4 Oct 21 11:29:36 Kassandra kernel: input: Touchscreen passthrough as /devices/virtual/input/input5 Oct 21 11:29:36 Kassandra kernel: input: Keyboard passthrough as /devices/virtual/input/input6 Oct 21 11:31:20 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:31:20 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:31:22 Kassandra kernel: x86/split lock detection: #AC: CNet Encrypt:0/8059 took a split_lock trap at address: 0x2296549f Oct 21 11:31:22 Kassandra kernel: x86/split lock detection: #AC: CJobMgr::m_Work/8090 took a split_lock trap at address: 0x2296549f Oct 21 11:34:22 Kassandra kernel: x86/split lock detection: #AC: CNet Encrypt:0/18681 took a split_lock trap at address: 0x566372cf Oct 21 11:35:56 Kassandra emhttpd: spinning down /dev/sde Oct 21 11:36:59 Kassandra emhttpd: read SMART /dev/sde Oct 21 11:40:38 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:40:48 Kassandra kernel: x86/split lock detection: #AC: CGameStreamVide/9066 took a split_lock trap at address: 0x60252c32 Oct 21 11:40:49 Kassandra kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input7 Oct 21 11:40:56 Kassandra emhttpd: spinning down /dev/sdd Oct 21 11:42:00 Kassandra emhttpd: read SMART /dev/sdd Oct 21 11:42:45 Kassandra kernel: x86/split lock detection: #AC: steam/7501 took a split_lock trap at address: 0x229654da Oct 21 11:42:45 Kassandra kernel: x86/split lock detection: #AC: CGameStreamVide/16154 took a split_lock trap at address: 0x229654da Oct 21 11:42:46 Kassandra kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input8 Oct 21 11:48:21 Kassandra acpid: input device has been disconnected, fd 10 Oct 21 11:48:23 Kassandra monitor: Stop running nchan processes Oct 21 11:48:46 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:48:49 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:48:52 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:48:52 Kassandra kernel: traps: light-locker[6690] trap int3 ip:145d468c87d7 sp:7fffea48d4f0 error:0 in libglib-2.0.so.0.7400.6[145d4688a000+8d000] Oct 21 11:48:53 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:48:53 Kassandra kernel: input: Logitech Wireless Mouse PID:4038 as /devices/virtual/input/input9 Oct 21 11:48:53 Kassandra kernel: input: Touchscreen passthrough as /devices/virtual/input/input10 Oct 21 11:48:53 Kassandra kernel: input: Keyboard passthrough as /devices/virtual/input/input11 Oct 21 11:48:57 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Oct 21 11:48:57 Kassandra kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-D-0 Quote Link to comment
MarianKoniuszko Posted October 24, 2023 Share Posted October 24, 2023 Hello, @Josh.5 can You provide some info about Lutris? I install with `apt get` and configure my games. Everything work fine until today. I noticed I don't have Lutris installed anymore. Regards. Quote Link to comment
Coastal Custom Tech Posted November 1, 2023 Share Posted November 1, 2023 On 7/7/2023 at 12:13 PM, Josh.5 said: Fixes issues with EmuDeck. This should now work exactly the same as it would on a Steam Deck. for the life of me I cant seem to get this to work as it should according to their instructions for install. I have the file on the desktop and tried opening with "software" but it gives a error about not being compatible. Quote Link to comment
devance Posted November 2, 2023 Share Posted November 2, 2023 Hi, first of all thanks @Josh.5for this awesome container. Got everything running and used it quite a lot already. Now I let the container run idling for some time and it uses more RAM the more time passes. I restarted the container around 32 hours ago and did not do anything with it at all and today my server RAM consumption was much higher than usual and I did some research and saw that my steam-headless container uses over 13GB of RAM from around like 2-3 GB after restarting it. This seems to me that there is some kind of memory leak. Its not really that problematic but does it happen for anyone else as well? Quote Link to comment
enJOyIT Posted November 5, 2023 Share Posted November 5, 2023 (edited) I can't get the server working for weeks now. It worked before, but suddenly it stopped... I can't get into WebGui. It has something to do with xorg: 2023-11-05 11:28:20,213 INFO spawned: 'x11vnc' with pid 1627 2023-11-05 11:28:21,215 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:21,215 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:21,218 WARN exited: desktop (exit status 11; not expected) 2023-11-05 11:28:22,220 INFO spawned: 'desktop' with pid 1650 2023-11-05 11:28:23,230 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:23,230 INFO reaped unknown pid 1656 (exit status 0) 2023-11-05 11:28:23,684 WARN exited: xorg (exit status 11; not expected) 2023-11-05 11:28:24,687 INFO spawned: 'xorg' with pid 1690 2023-11-05 11:28:25,689 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:34,714 WARN exited: xorg (exit status 11; not expected) 2023-11-05 11:28:35,716 INFO spawned: 'xorg' with pid 1835 2023-11-05 11:28:36,718 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:45,741 WARN exited: xorg (exit status 11; not expected) 2023-11-05 11:28:46,744 INFO spawned: 'xorg' with pid 1980 2023-11-05 11:28:47,746 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:50,492 WARN exited: sunshine (exit status 11; not expected) 2023-11-05 11:28:50,492 WARN exited: x11vnc (exit status 11; not expected) 2023-11-05 11:28:50,494 INFO spawned: 'x11vnc' with pid 2030 2023-11-05 11:28:50,496 INFO spawned: 'sunshine' with pid 2032 2023-11-05 11:28:51,497 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-05 11:28:51,497 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) my docker run: docker run -d --name='steam-headless' --net='eth1' --ip='192.168.20.115' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unraid" -e HOST_CONTAINERNAME="steam-headless" -e 'USER_PASSWORD'='xxxx' -e 'TZ'='Europe/Berlin' -e 'USER_LOCALES'='de_DE.UTF-8 UTF-8' -e 'WEB_UI_MODE'='vnc' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-9155e6ad-cdc3-137e-786a-3f45292a5ceb' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':55' -e 'MODE'='primary' -e 'PORT_NOVNC_WEB'='8083' -e 'ENABLE_VNC_AUDIO'='false' -e 'ENABLE_EVDEV_INPUTS'='false' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8083]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/docker/appdata/steam-headless':'/home/default':'rw' -v '/mnt/cache/games/':'/mnt/games':'rw' --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart=unless-stopped --shm-size=2G --ipc="host" -v '/tmp/.X11-unix':'/tmp/.X11-unix':'rw' -v '/tmp/tmp/pulse':'/tmp/tmp/pulse':'rw' -v '/dev/input':'/dev/input':'ro' --ulimit nofile=1024:524288 --runtime=nvidia 'josh5/steam-headless:latest' 03b1acf60cdca9bc0620d407d1f298b90165138459f1a706ae63e2a230194add I tried with/with out dummy plug, Display ID 0,1,55 ... Same behaviour On my unraid host: root@unraid:/tmp/.X11-unix# ls run/ Is there something missing here? I don't know what I can do else?! Maybe somebody has an idea? Thanks! P.S. GPU is an RTX A2000 Edited November 5, 2023 by enJOyIT Quote Link to comment
Frozn Posted November 5, 2023 Share Posted November 5, 2023 I can't seem to figure out how to get lutris installed. I open system>software tab and it opens to a blank UI with no apps in it. Tried to find the discord for this but the unmanic link in the first page doesn't work and it's not listed anywhere. Quote Link to comment
daemon9th Posted November 6, 2023 Share Posted November 6, 2023 21 hours ago, Frozn said: I can't seem to figure out how to get lutris installed. I open system>software tab and it opens to a blank UI with no apps in it. Tried to find the discord for this but the unmanic link in the first page doesn't work and it's not listed anywhere. Same for me, also an empty store. No luck with the discord either. Quote Link to comment
illiewillie Posted November 7, 2023 Share Posted November 7, 2023 (edited) Hello, thanks for this amazing container. Any plans to update sunshine to v0.21.0 in the near future? edit: nvm, it's not updated in the debian repositories Edited November 7, 2023 by illiewillie . Quote Link to comment
stry8993 Posted November 16, 2023 Share Posted November 16, 2023 (edited) Hey folks, sorry to bug ya. I did DM Avesynth, who was trying too, and succeeded in, setting this up with a reverse proxy to access it over the internet when away from home. Is there any written guidance, videos, etc, for this? Also, if its better to use the discord, where might I find that? Edited November 16, 2023 by stry8993 Quote Link to comment
Frozn Posted November 17, 2023 Share Posted November 17, 2023 On 11/6/2023 at 6:53 AM, daemon9th said: Same for me, also an empty store. No luck with the discord either. I ended up able to install lutris using flatpak flatpak install flathub net.lutris.Lutris and also using sudo apt-get update and sudo apt-get upgrade solved the software app being empty, I think maybe it was out of date. Looks like the discord link is fixed now too. Quote Link to comment
daemon9th Posted November 18, 2023 Share Posted November 18, 2023 On 11/17/2023 at 1:16 AM, Frozn said: I ended up able to install lutris using flatpak flatpak install flathub net.lutris.Lutris and also using sudo apt-get update and sudo apt-get upgrade solved the software app being empty, I think maybe it was out of date. Looks like the discord link is fixed now too. Great, that worked! Thanks for returning with a solution Quote Link to comment
Mrtj18 Posted November 23, 2023 Share Posted November 23, 2023 On 11/2/2023 at 4:31 AM, devance said: Hi, first of all thanks @Josh.5for this awesome container. Got everything running and used it quite a lot already. Now I let the container run idling for some time and it uses more RAM the more time passes. I restarted the container around 32 hours ago and did not do anything with it at all and today my server RAM consumption was much higher than usual and I did some research and saw that my steam-headless container uses over 13GB of RAM from around like 2-3 GB after restarting it. This seems to me that there is some kind of memory leak. Its not really that problematic but does it happen for anyone else as well? This was happening to me as well. I had to reset the container every 2 days or so, when I had 32G of RAM. If I didn't the container would eventually eat all my available RAM and start causing server issues. Oddly once I upgraded to 64G of RAM I haven't had this issue. Very odd indeed. Quote Link to comment
Napoleon Posted November 26, 2023 Share Posted November 26, 2023 I've got an issue with this, it installs, I open VNC, log in but steam doesn't show despite being open. If I right click it'll show the right click menu and this changes depending on where the cursor is on the screen but it just shows the desktop. Tried many restarts and open/reopen. It comes up on other devices as available. Quote Link to comment
Flon22 Posted November 27, 2023 Share Posted November 27, 2023 Hey all, I'm getting the xorg issue that I've seen described in this thread a few times, however their fixes haven't worked for me. The container starts, but vnc isnt able to connect. The logging shows that XOrg failed to start. I dont have any other dockers outputting to the gpu. I have a VM that does output to the gpu but it doesn't run all the time. My unraid also isnt displaying a gui. I have a Radeon rx580, and the Radeon TOP plugin installed. It appears to be recognised in the logging. If someone wouldnt mind giving me a hand I'd really appreciate it, thanks! SteamHeadlessLogCopy.txt docker run -d --name='steam-headless' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Wiggum" -e HOST_CONTAINERNAME="steam-headless" -e 'USER_PASSWORD'='password' -e 'TZ'='Europe/London' -e 'USER_LOCALES'='en_US.UTF-8 UTF-8' -e 'NVIDIA_PATCH_VERSION'='' -e 'WEB_UI_MODE'='vnc' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':0' -e 'MODE'='primary' -e 'PORT_NOVNC_WEB'='8083' -e 'ENABLE_VNC_AUDIO'='true' -e 'ENABLE_EVDEV_INPUTS'='false' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8083]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/user/appdata/steam-headless':'/home/default':'rw' -v '/mnt/user/games':'/mnt/games':'rw' --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart='unless-stopped' --shm-size='2G' --ipc='host' -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' --ulimit='nofile=1024:524288' --device='/dev/fuse' --device='/dev/uinput' --device-cgroup-rule='c 13:* rmw' --cap-add='NET_ADMIN' --cap-add='SYS_ADMIN' --cap-add='SYS_NICE' --security-opt='seccomp=unconfined' 'josh5/steam-headless:latest' 815bb4c81bf960720b96fc6e352576fac97049c328b41865f6a413d0fdbf2664 Quote Link to comment
survivor182ca Posted November 28, 2023 Share Posted November 28, 2023 Stop using vnc and use sunshine/moonlight that is WAY better. Quote Link to comment
SavellM Posted November 29, 2023 Share Posted November 29, 2023 (edited) So few things... I've just spun up this container and so far nice! Got Steam up and running. For games that say 'Runs on Windows' do you just go into force compatibility? Secondly, I was looking at installing some bits, but it needs to do a apt install, I noticed there are a ton of updates to do right out of the box. Is it safe to do this? I tried to apt update, but it just hung at 22% *edit*: I saw in unRAID logs: Nov 29 16:31:08 Namek login: pam_unix(login:auth): check pass; user unknown Nov 29 16:31:08 Namek login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost= Nov 29 16:31:10 Namek login: FAILED LOGIN 3 FROM tty1 FOR full-upgrade, Authentication failure Not sure if it helps diagnose the upgrading? I was running the command as sudo apt-get full-upgrade Thirdly, I was trying to get steam to install games onto my NVME but it took forever to 'Reserve Space' - is this normal? Fourth, I launch a game, seems to be fine, but it never actually loads or plays, it says Launching and then Changes to STOP, but nothing displays, there is no game. Then eventually it just goes back to 'Play' like the game gets stopped automatically. I have noticed: Nov 30 14:46:55 Namek kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-0 In unRAID logs. I do have a DP dummy plug installed. Even trying Steam-Link play nothing happens, games dont load. For reference I have passed through a Quadro P2000 to test. I know it's not a gaming card, but I wanted to check before I purchased a GPU just for this. But so far no luck... Games dont load and I just get kicked back to desktop @Josh.5 any help would be massively appreciated. I would join Discord but the link for whatever reason doesn't work Edited November 30, 2023 by SavellM Quote Link to comment
Recommended Posts
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.