Open bpvarsity opened 7 months ago
alansari
commented
7 months ago How are you running the container? should be run with host networking is my first guess. But if you are using the template without any changes that should already be set, so my next guess is you might be using a vpn, tailscale, traefik, or some other reverse proxy setup. If you need help with this jump on discord!
apclapp
commented
5 months ago @bpvarsity -- In case you were still having this issue, I found your post after seeing an identical pattern of error messages.
My environment is slightly different, running under Docker on Unraid.
I found that in my situation, I was using an older set of launch parameters. Reviewing and updating these solved my issue. (For Unraid users, these are found by clicking 'edit' on a Docker container, then toggling the 'Advanced' slide-toggle in the top-right of the UI, and then edit the textbox labeled "Extra Parameters".
My old parameters, which resulted in errors were as follows (reformatted for ease of reading):
--hostname='SteamHeadless'
--restart=unless-stopped
--runtime=nvidia
--add-host='SteamHeadless:127.0.0.1'
--shm-size=2G
--ipc="host"
--ulimit nofile=1024:524288
-v '/tmp/.X11-unix':'/tmp/.X11-unix':'rw'
-v '/tmp/tmp/pulse':'/tmp/tmp/pulse':'rw'
-v '/dev/input':'/dev/input':'ro' The updated launch parameters, which got things working correctly, were as follows:
--hostname='SteamHeadless'
--restart=unless-stopped
--runtime=nvidia
--add-host='SteamHeadless:127.0.0.1'
--shm-size='2G'
--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'
-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' Hopefully this is helpful for your situation as well. Also, do note that I'm using the --runtime=nvidia parameter because I am in an nvidia environment. Of course you can drop/alter this as it applies to you.
trgkyle
commented
4 months ago @bpvarsity -- In case you were still having this issue, I found your post after seeing an identical pattern of error messages.
My environment is slightly different, running under Docker on Unraid.
I found that in my situation, I was using an older set of launch parameters. Reviewing and updating these solved my issue. (For Unraid users, these are found by clicking 'edit' on a Docker container, then toggling the 'Advanced' slide-toggle in the top-right of the UI, and then edit the textbox labeled "Extra Parameters".
My old parameters, which resulted in errors were as follows (reformatted for ease of reading):
--hostname='SteamHeadless' --restart=unless-stopped --runtime=nvidia --add-host='SteamHeadless:127.0.0.1' --shm-size=2G --ipc="host" --ulimit nofile=1024:524288 -v '/tmp/.X11-unix':'/tmp/.X11-unix':'rw' -v '/tmp/tmp/pulse':'/tmp/tmp/pulse':'rw' -v '/dev/input':'/dev/input':'ro'The updated launch parameters, which got things working correctly, were as follows:
--hostname='SteamHeadless' --restart=unless-stopped --runtime=nvidia --add-host='SteamHeadless:127.0.0.1' --shm-size='2G' --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' -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'Hopefully this is helpful for your situation as well. Also, do note that I'm using the --runtime=nvidia parameter because I am in an nvidia environment. Of course you can drop/alter this as it applies to you.
Thanks, I got same problem and its seem this problem was fixed by follow your config but I got another error
Build: [2024-02-10 02:35:31] [master] [6cc9f56155f3c7f9fc6bc9c22ef2cbf555029c00] [debian]
[ /etc/cont-init.d/10-setup_user.sh: executing... ] Configure default user
[ /etc/cont-init.d/11-setup_sysctl_values.sh: executing... ] Configure some system kernel parameters
[ /etc/cont-init.d/30-configure_dbus.sh: executing... ] Configure container dbus
[ /etc/cont-init.d/30-configure_udev.sh: executing... ] Configure udevd
[ /etc/cont-init.d/40-setup_locale.sh: executing... ] Configure local
[ /etc/cont-init.d/50-configure_pulseaudio.sh: executing... ] Configure pulseaudio
[ /etc/cont-init.d/60-configure_gpu_driver.sh: executing... ] Found Intel device 'Intel(R) Core(TM) i9-14900K'
[ /etc/cont-init.d/70-configure_desktop.sh: executing... ] Configure Desktop
[ /etc/cont-init.d/70-configure_xorg.sh: executing... ] Generate NVIDIA xorg.conf
WARNING: Unable to locate/open X configuration file.
Option "ProbeAllGpus" "False" added to Screen "Screen0". Option "BaseMosaic" "False" added to Screen "Screen0". Option "AllowEmptyInitialConfiguration" "True" added to Screen "Screen0". New X configuration file written to '/etc/X11/xorg.conf'
DONE
[ /etc/cont-init.d/80-configure_flatpak.sh: executing... ] Configure Flatpak mount: /proc: cannot mount none read-only. dmesg(1) may have more information after failed mount system call.
alansari
commented
4 months ago you might want to try after removing these lines: -v '/dev/input/':'/dev/input/':'ro' -v '/run/udev/data/':'/run/udev/data/':'ro' I believe you also don't need: -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' unless you are sharing the X11 or pulse socket with other containers.
Though my best guess is your running on ubuntu/debian host and you need: security_opt:
Describe the Bug
Tried the latest debian image and one from 2 months ago. Using template docker compose and .env and only change was runtime to nvidia.
I can view the web ui login paid but get a failed to connect to server. It seems to be stuck in a loop with
2023-11-29 04:25:52,784 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-29 04:25:52,784 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-11-29 04:25:52,784 INFO reaped unknown pid 962 (exit status 0) 2023-11-29 04:25:54,547 WARN exited: xorg (exit status 11; not expected) 2023-11-29 04:25:54,548 INFO spawned: 'xorg' with pid 989 2023-11-29 04:25:55,550 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Steps to Reproduce
No response
Expected Behavior
No response
Screenshots
No response
Relevant Settings
No response
Version
Build: [2023-09-29 21:48:12] [0.2.0] [f4cad0aab007ca30d399dd44b79a173872dd3f07] [debian]
Platform
Debian GNU/Linux - 12 (bookworm) 6.1.0-13-amd64 unknown unknown GNU/Linux | NVIDIA-SMI 525.125.06 Driver Version: 525.125.06 CUDA Version: 12.0 | Docker version 20.10.24+dfsg1, build 297e128
Relevant log output