[Support] Josh5 - Steam (Headless)


Recommended Posts

44 minutes ago, Josh.5 said:

What changed since this ^

Because I'm outta town right now a friend of mine is testing the card. Only wanted to give the info back that the output is mirrored. Will probably take another look at the weekend why I'm having problems with that 

Link to comment

One of the recent updates is causing my gpu to not go to a sleep state. Would go to P8 after a single login. Now it goes to sleep mode for a second or two and then goes back to P0. Not sure what caused it

Edited by spdelope
spelling
Link to comment

Hey, its me again with the dns issue. I was able to setup the the container so it could connect to the lancache which is running in a container using br0 network mode. The trick was to sett the --dns entry first in the extra parameters field (i tried it last, which somehow didnt work?). Though now i am facing another issue: For the controller support, if i understood that correctly, i need the uinput plugin and the steam-headless container has to be in host network mode, but there lays the problem as the container in host mode cant contact containers running in br0 on the same docker host, so currently i can either use controller support or lancache support. Is it possible to alter this container so it is able to use the uinput plugin even in br0 network mode? Or any idea how to make it communicate with containers in br0 while being in the host network mode?

Link to comment

first of all, this is awesome, thank you for sharing. I was able to install and get it up and running. I am accessing via noVNC with no major issues. However the resolution of the desktop in noVNC is 1024x768, and the settings dont allow me to choose anything higher or with a 16:9 aspect ratio. Any ideas? I am not running a GPU on this machine, it has a i7-4790. I just want to set it to 1920x1080 if possible. 

Link to comment
1 hour ago, mdezzi said:

first of all, this is awesome, thank you for sharing. I was able to install and get it up and running. I am accessing via noVNC with no major issues. However the resolution of the desktop in noVNC is 1024x768, and the settings dont allow me to choose anything higher or with a 16:9 aspect ratio. Any ideas? I am not running a GPU on this machine, it has a i7-4790. I just want to set it to 1920x1080 if possible. 

I have not yet setup the container to fake a real display yet. I personally am using an HDMI dummy plug.

Link to comment
4 hours ago, mdezzi said:

first of all, this is awesome, thank you for sharing. I was able to install and get it up and running. I am accessing via noVNC with no major issues. However the resolution of the desktop in noVNC is 1024x768, and the settings dont allow me to choose anything higher or with a 16:9 aspect ratio. Any ideas? I am not running a GPU on this machine, it has a i7-4790. I just want to set it to 1920x1080 if possible. 

You can connect a real display but don't need to switch to the output. The container regognized the display for my site so you could change the resolution if you want or you buy maybe a hdmi dummy plug works really well. 

Link to comment

So I installed the uinput plugin, I verified the module is loaded and setup the container as directed with net:host. I do get an additional notification from steam now about the virtual input and there's kernel log events about the controller. It works for big picture but still can't get any games to recognize it no matter what...

 

EDIT: I went through the trouble of getting a steam controller out of storage to test with that as well. It's connected through Bluetooth, and steam recognizes it too in big picture, but it won't work with any games.

Edited by JimTebo
Link to comment
On 1/18/2022 at 6:16 AM, Josh.5 said:

What changed since this ^

I got my display working. The container uses the HDMI port of the card. The docker set the refresh rate to 120 HZ which my monitor can't handle over HDMI. So now I only need to get the card out of idle mode and I don't now what is causing this. 

Link to comment

@Josh.5 nice to see some new updates from you. I'm trying the Epic store right now with the Heroic Games Launcher and realized that the docker is missing a Wine version natively. Maybe you could add this in the next update.

 

I passed through my peripherals (mouse and keyboard) and it works perfectly, only needed to remove some lines in the extra parameter. 

 

My only problem still is that my gpu states that it is throttling even if I change the power mode in the x server driver. So this seems not to be a problem with your docker. 

Link to comment
On 1/11/2022 at 4:51 PM, Sqibble said:

Going over the logs I found some things referring to localhost.

 

in /mnt/user/appdata/steam-headless/.cache/xorg.err there's:

tcpserver: fatal: temporarily unable to figure out IP address for localhost: network unreachable

 

and in /mnt/user/appdata/steam-headless/.cache/x11vnc.err:

10/01/2022 17:41:06 x11vnc version: 0.9.16 lastmod: 2019-01-05  pid: 185
10/01/2022 17:41:06 XOpenDisplay(":0") failed.
10/01/2022 17:41:06 Trying again with XAUTHLOCALHOSTNAME=localhost ...

 

This led me to reconsider my network settings. I had the container set to use br0, changed it to host and changed the extra parameter --hostname='steam-headless' to my device's hostname. And now it boots. Not sure why it didn't work for me using br0 but I don't think the problem is with your container.

 

 So thanks for your time and sorry for wasting it 😅

HI there!
So I'm getting this same issue now.. I wasn't before and I don't know what changed.

When you say you changed hostname to device hostname, which do you mean? like if my unraid server was named bosh should i change it to --hostname='bosh'  ?

Thanks for any help!

Link to comment
1 hour ago, HellraiserOSU said:

HI there!
So I'm getting this same issue now.. I wasn't before and I don't know what changed.

When you say you changed hostname to device hostname, which do you mean? like if my unraid server was named bosh should i change it to --hostname='bosh'  ?

Thanks for any help!

No, the hostname param will do nothing to solve this. However, you should be running the container on the host network.

If you are running into issues, please first make sure you are using the most up-to-date template published in the CA store. Also be sure to follow through the setup guide in the first post of this forum thread.

Link to comment
On 1/17/2022 at 1:42 AM, Josh.5 said:

@[RIVINS]  @Mobious
Try google the error "Unable to load filesystem_steam.so". Looks like there are some issues with steam and XFS file systems for some games. I have not looked into this, but let me know if you find a fix that can be applied to the container or Unraid configuration.

 

I had the same error when trying to run Portal - my array is xfs. 

 

to workaround I moved my /games to the cache (unencrypted - btrfs) drive. Not a perfect solution but one that works for me.

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

No, the hostname param will do nothing to solve this. However, you should be running the container on the host network.

If you are running into issues, please first make sure you are using the most up-to-date template published in the CA store. Also be sure to follow through the setup guide in the first post of this forum thread.

 

Hmm so I didn't do anything and it seems to be working again. It asked me to reboot again because of new nvidia drivers..  And I tried rebooting the server before and still got the same error.. so maybe the new nvidia drivers fixed it? I dunno :)

Link to comment

For the record:

I5/10 series. 64Gb Ram. I have a P2000 that is used for emby. I added a 1080 and set it up for use with this container. No issues. I also connect to unraid via tailscale. That same ip worked to connect to noVNC to access steam.

 

Running Fedora on my x270, used the flatpak version of steam link, connection is great over wifi. Next week Ill see what it is like via tailscale / WAN. Downloading some fps games to really test it out.

Link to comment

I just got this setup with a 3060 and everything loads great. But controller input is not working.

I have the controller plugin installed and the docker configured in host mode.

Is there anything else I need to do?

Testing with my iPhone and Apple TV with the steam link app.

The touch controls in game also don’t seem to work…

Host is:
8th gen I5
64 gb ram
Nvidia 3060 12GB

Remote devices:
Apple TV 4K + Xbox Series S/X controller over BT
iPhone 13 Pro with touch controls

I will keep messing with it because I had just gotten it set up.


Sent from my iPhone using Tapatalk

Link to comment

so iam into this, i need to know if i can passtrough my whole usb Controller to this debian Docker and how it is done.

 

right now i try to pass my XBox dongle via 

 

/dev/bus/usb/001/002

 

but there is no indication inside the docker that this worked.

 

since the Unraid server is right next to my TV i would not need to stream that would be MUCH better.

 

there are no options inside debian to find any sort of controller.

 

when i lspci inside the docker it shows me all Unraid devices so it should be possible.

Edited by domrockt
Link to comment

Hello! I am back to having this error... clean install too.. I deleted app_data for steam headless

 

2022-01-29 17:58:16,090 INFO spawned: 'novnc' with pid 150
2022-01-29 17:58:16,091 INFO spawned: 'x11vnc' with pid 151
2022-01-29 17:58:16,091 INFO spawned: 'desktop' with pid 152
2022-01-29 17:58:16,099 INFO reaped unknown pid 169 (exit status 0)
2022-01-29 17:58:16,113 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:17,083 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:17,087 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,087 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,088 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,093 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,093 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,186 INFO spawned: 'desktop' with pid 312
2022-01-29 17:58:17,195 INFO reaped unknown pid 317 (exit status 0)
2022-01-29 17:58:17,209 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:18,250 INFO spawned: 'x11vnc' with pid 329
2022-01-29 17:58:19,257 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:19,258 INFO spawned: 'desktop' with pid 330
2022-01-29 17:58:19,258 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:19,259 INFO spawned: 'x11vnc' with pid 331
2022-01-29 17:58:19,268 INFO reaped unknown pid 336 (exit status 0)
2022-01-29 17:58:19,280 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:20,266 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:20,266 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:21,095 INFO spawned: 'x11vnc' with pid 348
2022-01-29 17:58:22,105 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:22,106 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:23,109 INFO spawned: 'x11vnc' with pid 349
2022-01-29 17:58:23,110 INFO spawned: 'desktop' with pid 350
2022-01-29 17:58:23,121 INFO reaped unknown pid 355 (exit status 0)
2022-01-29 17:58:23,136 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:23,866 INFO gave up: desktop entered FATAL state, too many start retries too quickly
2022-01-29 17:58:24,116 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:24,117 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:25,120 INFO spawned: 'x11vnc' with pid 367
2022-01-29 17:58:26,127 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:26,128 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:27,130 INFO spawned: 'x11vnc' with pid 368
2022-01-29 17:58:28,137 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:28,138 INFO exited: x11vnc (exit status 1; not expected)

 

I am running as host..

image.thumb.png.a594e69573892f5498f0815514a2bb1c.png

 

I've tried secondary display, :0 as  display ID, changing WebUi to a different port..

image.thumb.png.43e81e89f3c07a0fb545ba377eea1051.png

 

I can't get it to run again..

 

--Update--

Opening Desktop.err.log I'm getting

 

ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'

 


Changing to a different number gave the same error

and changing it to :0 gave the same

xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused

Edited by HellraiserOSU
Link to comment
Hello! I am back to having this error... clean install too.. I deleted app_data for steam headless
 
2022-01-29 17:58:16,090 INFO spawned: 'novnc' with pid 1502022-01-29 17:58:16,091 INFO spawned: 'x11vnc' with pid 1512022-01-29 17:58:16,091 INFO spawned: 'desktop' with pid 1522022-01-29 17:58:16,099 INFO reaped unknown pid 169 (exit status 0)2022-01-29 17:58:16,113 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:17,083 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:17,087 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,087 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,088 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,093 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,093 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,186 INFO spawned: 'desktop' with pid 3122022-01-29 17:58:17,195 INFO reaped unknown pid 317 (exit status 0)2022-01-29 17:58:17,209 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:18,250 INFO spawned: 'x11vnc' with pid 3292022-01-29 17:58:19,257 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:19,258 INFO spawned: 'desktop' with pid 3302022-01-29 17:58:19,258 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:19,259 INFO spawned: 'x11vnc' with pid 3312022-01-29 17:58:19,268 INFO reaped unknown pid 336 (exit status 0)2022-01-29 17:58:19,280 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:20,266 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:20,266 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:21,095 INFO spawned: 'x11vnc' with pid 3482022-01-29 17:58:22,105 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:22,106 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:23,109 INFO spawned: 'x11vnc' with pid 3492022-01-29 17:58:23,110 INFO spawned: 'desktop' with pid 3502022-01-29 17:58:23,121 INFO reaped unknown pid 355 (exit status 0)2022-01-29 17:58:23,136 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:23,866 INFO gave up: desktop entered FATAL state, too many start retries too quickly2022-01-29 17:58:24,116 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:24,117 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:25,120 INFO spawned: 'x11vnc' with pid 3672022-01-29 17:58:26,127 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:26,128 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:27,130 INFO spawned: 'x11vnc' with pid 3682022-01-29 17:58:28,137 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:28,138 INFO exited: x11vnc (exit status 1; not expected)

 
I am running as host..
image.thumb.png.a594e69573892f5498f0815514a2bb1c.png
 
I've tried secondary display, :0 as  display ID, changing WebUi to a different port..
image.thumb.png.43e81e89f3c07a0fb545ba377eea1051.png
 
I can't get it to run again..
 
--Update--
Opening Desktop.err.log I'm getting
 
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'
 

Changing to a different number gave the same error
and changing it to :0 gave the same
xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused

Is xorg starting?
Link to comment
31 minutes ago, domrockt said:

there is no controller support in the Debian Distro what so ever, could there be the culprit?

Sorry, I have not tried to use the container for this reason. If you do figure it out, please post some details here so that others can also set theirs up in the same way that you are trying to.

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.