-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Failed to connect to server #116
Comments
I am also seeing this issue but with only onboard graphics: |
Yeah this was tested with trunc when i have an nvidia card but both gave me errors |
Same issue, same logs Ubuntu Server Ubuntu 22.04.3 LTS |
I have a same issue. i wget the .env and the docker compose fron github, so it is unmodified, but xserver fails to load. |
Same here, running unmodified config from the quickstart guide on headless debian installation (running on an AMD laptop with integrated graphics)
The container keeps looping that error every few seconds |
Hey !
|
Also seeing the same on an unraid server with an amd card, privileged mode, host networking. lscpi in the container shows that it can see the card. Not sure how to debug further. |
Ah the xorg log file in the container gives some clues. I have integrated graphics powering the main unraid UI. Nothing is plugged into the radeon card. Xorg is failing with "device or resource busy"
|
It seems we need a way to tell the container which device to use. I think based on that xorg log it is also trying to initialize the integrated graphics, which are already running a server, hence the "device or resource busy". |
OK confirmed that's the issue. I restarted the unraid server in no gui mode and I can now connect to the steam docker container through vnc. Not quite sure how to tell the container which GPU/display to use to work around this if I want to boot unraid in ui mode again. |
Mine turned out to (probably) be a bug with proxmox on some AMD processors, especially threadrippers. Setting CPU to "host" causes an innumerable amount of issues on proxmox 8.0.4. I'm not sure exactly what the actual cause of the error in the VM was, all I know is that setting kvm ignore_msrs=1 (which I did for another unrelated issue in another VM) fixed it. I run a 1950x on proxmox 8.0.4, Ubuntu virtual machine, with a nvidia 3060 passed through. echo "options kvm ignore_msrs=1" > /etc/modprobe.d/kvm.conf on the host. |
Describe the Bug
Getting the error
Failed to connect to server
Steps to Reproduce
Expected Behavior
Click connect and connect
Screenshots
No response
Relevant Settings
Default .env
Version
Build: [2023-12-09 02:38:11] [master] [6cc9f56] [debian]
Platform
Arch Linux 6.6.6-arch1-1
NVIDIA-SMI 545.29.06 Driver Version: 545.29.06 CUDA Version: 12.3
Docker version 24.0.7, build afdd53b4e3
Docker Compose version 2.23.3
Relevant log output
The text was updated successfully, but these errors were encountered: