The container compile well but I get permission problem for vnc and the other stuff when I run it. Is there something to do additionnaly when you compile the image????

Edited May 10, 20232 yr by survivor182ca

Also for amd gpu we should either :

 

- point to unstable repo of bulleye to get mesa that is not 100 year old or

- use bookworm base image (debian)

 

Otherwise most windows/proton games are not working

2023-05-10 01:25:14,207 INFO spawnerr: command at '/usr/bin/start-xorg.sh' is not executable
2023-05-10 01:25:14,207 INFO spawnerr: command at '/usr/bin/start-x11vnc.sh' is not executable

2023-05-10 01:27:12,394 INFO exited: desktop (exit status 11; not expected)
2023-05-10 01:27:12,407 INFO spawned: 'desktop' with pid 1581
2023-05-10 01:27:12,408 INFO exited: sunshine (exit status 11; not expected)

Dockerfile Here is my Dockerfile file that fix the permission for VNC, Sunshine and AMD gpu

 

IMPORTANT : For the first time you start the container you have to log into the container and execute this command to get the latest mesa : apt-get upgrade -y

 

Tested with APEX legend legend,Asphalt 9, CS go, Team Forteress 2, The Expendabros

Quick question, I'm trying to use the Docker container for the output on the HDMI port of the NVidia GPU. Is there a way to configure the container in its current form so that the audio device (of the NVidia GPU via HDMI) is correctly adopted? Currently, only the dummy output is configured. Or have I overlooked something? 
Best regards

On 5/18/2023 at 6:51 PM, Apotessar said:

Quick question, I'm trying to use the Docker container for the output on the HDMI port of the NVidia GPU. Is there a way to configure the container in its current form so that the audio device (of the NVidia GPU via HDMI) is correctly adopted? Currently, only the dummy output is configured. Or have I overlooked something? 
Best regards

Yes, I actually managed to do this myself. You need to manually install the plugin here to enable audio drivers on your unraid machine: https://github.com/ich777/unraid-sound-driver
Then within the /home/default/init.d directory I added a new script called audioPermissions.sh:
 

getent group audio2 || groupadd -g 17 audio2 && usermod -a -G audio2 default

This should fix the permissions issue where there's a mismatch with the audio group.

Then restart your steam-headless container and it should have audio on startup.

I think there's a problem with the lastest Nvidia Drivers v535.43.02 that cause the Xorg server to panic in the docker.

 

Reverting back to the New Feature Branch v530.41.03 got Xorg working again.

Edited June 1, 20232 yr by Asthal

Can someone help me with setting up sunshine? I have changed the sunshine.conf to settings to lan but when I run sunshine in the terminal I get this error.

 

[2023:06:01:21:05:11]: Info: Open the Web UI to set your new username and password and getting started
[2023:06:01:21:05:11]: Fatal: Couldn't bind RTSP server to port [48010], Address already in use
[2023:06:01:21:05:11]: Info: File /root/.config/sunshine/sunshine_state.json doesn't exist
[2023:06:01:21:05:11]: Fatal: Couldn't bind http server to ports [47989, 47989]: bind: Address already in use
[2023:06:01:21:05:11]: Fatal: Couldn't bind http server to ports [47990]: bind: Address already in use
[2023:06:01:21:05:11]: Error: Failed to create client: Daemon not running

 

I have changed the port within sunshine.conf but the ports here never change. Any help would be appericiated!

Edited June 1, 20232 yr by Rohit2122

On 6/1/2023 at 5:13 PM, Rohit2122 said:

Can someone help me with setting up sunshine? I have changed the sunshine.conf to settings to lan but when I run sunshine in the terminal I get this error.

 

[2023:06:01:21:05:11]: Info: Open the Web UI to set your new username and password and getting started
[2023:06:01:21:05:11]: Fatal: Couldn't bind RTSP server to port [48010], Address already in use
[2023:06:01:21:05:11]: Info: File /root/.config/sunshine/sunshine_state.json doesn't exist
[2023:06:01:21:05:11]: Fatal: Couldn't bind http server to ports [47989, 47989]: bind: Address already in use
[2023:06:01:21:05:11]: Fatal: Couldn't bind http server to ports [47990]: bind: Address already in use
[2023:06:01:21:05:11]: Error: Failed to create client: Daemon not running

 

I have changed the port within sunshine.conf but the ports here never change. Any help would be appericiated!

tl;dr for future people: go here: https://your-unraid-ip:47990 in any same-network browser

 

Did you figure it out?

 

Those errors are telling you, in order:

open the webUI to finish setup (sunshine devs should provide a link there, but, hey)

the port is being is being used (by sunshine which is already running- there's a .sh script which runs at this docker's startup)

the .json doesn't exist because the webUI setup hasn't been completed yet

since sunshine is running, all these ports are unavailable

nothing is running because sunshine is just sitting and waiting for the user to finish setup

 

to do so go to this url in any browser on the same network:

 

https://your-unraid-ip-here:47990

 

yes, it is https with a self-signed cert. i don't know why. just go with it.

ignore the cert warning because it's self-signed and you know that.

 

once you go to that url it's all very self-explanatory from there, but if you want a ton more info or questions go to the Sunshine official setup guide here: https://docs.lizardbyte.dev/projects/sunshine/en/latest/index.html

Forgive me, I feel like an idiot asking. 

How do I add an AppImage to the list of programs? I'm trying my damnest to add the Yuzu appimage and for whatever reason Steam won't accept it if I browse to it and add it as a non steam game. It worked in an earlier build, but I can't for the life of me get it to work now.

 

Edit: NM, I added another app an repathed/renamed the target. Still not sure why Steam won't add a browsed application.

Edited June 18, 20232 yr by mnovak

For sunshine : https://docs.lizardbyte.dev/projects/sunshine/en/latest/about/app_examples.html

Hey.

 

I having an issue running this container. I open the WebUI and it just says "Failed to connect to server.  No VNC."

It worked the very first time I opened it after install. Was able to sign in to my account. Had to close the window and come back later. After that, it started saying this. Nothing changed in my server. Not sure what happened. 

2 minutes ago, Ichithekiller said:

Hey.

 

I having an issue running this container. I open the WebUI and it just says "Failed to connect to server.  No VNC."

It worked the very first time I opened it after install. Was able to sign in to my account. Had to close the window and come back later. After that, it started saying this. Nothing changed in my server. Not sure what happened. 

 

Same problem here since updated to unraid 6.12 with Nvidia Driver 535.54.03

 

The log says :

2023-06-18 15:42:33,523 INFO spawned: 'x11vnc' with pid 5827
2023-06-18 15:42:34,524 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:42:37,325 INFO exited: desktop (exit status 11; not expected)
2023-06-18 15:42:37,327 INFO spawned: 'desktop' with pid 5858
2023-06-18 15:42:38,329 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:42:38,329 INFO reaped unknown pid 5862 (exit status 0)
2023-06-18 15:43:03,655 INFO exited: x11vnc (exit status 11; not expected)
2023-06-18 15:43:03,657 INFO spawned: 'x11vnc' with pid 6074
2023-06-18 15:43:04,658 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:43:07,470 INFO exited: desktop (exit status 11; not expected)
2023-06-18 15:43:07,472 INFO spawned: 'desktop' with pid 6105
2023-06-18 15:43:08,474 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:43:08,474 INFO reaped unknown pid 6109 (exit status 0)

 

 

44 minutes ago, Asthal said:

 

Same problem here since updated to unraid 6.12 with Nvidia Driver 535.54.03

 

The log says :

2023-06-18 15:42:33,523 INFO spawned: 'x11vnc' with pid 5827
2023-06-18 15:42:34,524 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:42:37,325 INFO exited: desktop (exit status 11; not expected)
2023-06-18 15:42:37,327 INFO spawned: 'desktop' with pid 5858
2023-06-18 15:42:38,329 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:42:38,329 INFO reaped unknown pid 5862 (exit status 0)
2023-06-18 15:43:03,655 INFO exited: x11vnc (exit status 11; not expected)
2023-06-18 15:43:03,657 INFO spawned: 'x11vnc' with pid 6074
2023-06-18 15:43:04,658 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:43:07,470 INFO exited: desktop (exit status 11; not expected)
2023-06-18 15:43:07,472 INFO spawned: 'desktop' with pid 6105
2023-06-18 15:43:08,474 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-18 15:43:08,474 INFO reaped unknown pid 6109 (exit status 0)

 

 

Downgrade your driver to v530.41.03

48 minutes ago, Ichithekiller said:

Hey.

 

I having an issue running this container. I open the WebUI and it just says "Failed to connect to server.  No VNC."

It worked the very first time I opened it after install. Was able to sign in to my account. Had to close the window and come back later. After that, it started saying this. Nothing changed in my server. Not sure what happened. 

Downgrade your driver to v530.41.03

6 hours ago, mnovak said:

Downgrade your driver to v530.41.03

Problem is that Unraid 6.12 recommend 535.54.03

2 hours ago, Asthal said:

Problem is that Unraid 6.12 recommend 535.54.03

I'm running 6.12 just fine with the other driver. You don't need to be on "Latest" for GPU. I assure you it'll be fine if you downgrade, and it will fix the container.

41 minutes ago, mnovak said:

I'm running 6.12 just fine with the other driver. You don't need to be on "Latest" for GPU. I assure you it'll be fine if you downgrade, and it will fix the container.

Right it did work. But now there's a bug related to the new version of steam : I can't add my /mnt/game folder anymore. Steam won't let me browse outside it's own folder.

On 6/18/2023 at 9:50 PM, Asthal said:

Right it did work. But now there's a bug related to the new version of steam : I can't add my /mnt/game folder anymore. Steam won't let me browse outside it's own folder.

 

Found the solution if someone else have the same problem :

 

Open the libraryfolders.vdf with a text editor in /home/default/.steam/debian-installation/steamapps/

 

Edit your file to add the folder mounted in unraid. It should look something like this :

 

"libraryfolders"
{
    "0"
    {
        "path"        "/home/default/.steam/debian-installation"
        "label"        ""
        "contentid"        "0"
        "totalsize"        "0"
        "update_clean_bytes_tally"        "0"
        "time_last_update_corruption"        "0"
        "apps"
        {
        }
    }
    "1"
    {
        "path"        "/mnt/games"
        "label"        "games"
        "contentid"        "0"
        "totalsize"        "0"
        "update_clean_bytes_tally"        "0"
        "time_last_update_corruption"        "0"
        "apps"
        {
        }
    }
}

On 6/18/2023 at 12:28 PM, mnovak said:

Downgrade your driver to v530.41.03

Ugh I don't think that driver will work with my card I have in there which is a RTX 4060 Ti. Hopefully it gets fixed sometime soon.

29 minutes ago, HellraiserOSU said:

Ugh I don't think that driver will work with my card I have in there which is a RTX 4060 Ti. Hopefully it gets fixed sometime soon.

You should probably try it before complaining, according to nvidia it works? 

16 minutes ago, mnovak said:

You should probably try it before complaining, according to nvidia it works? 

It might.. depends on the card. I've had to wait for drivers on some of the cards I reviewed or there would be stability and performance issues. Yes, the basic image would post, but there would be other factors that would make the card not work right without the correct drive.

1 minute ago, HellraiserOSU said:

It might.. depends on the card. I've had to wait for drivers on some of the cards I reviewed or there would be stability and performance issues. Yes, the basic image would post, but there would be other factors that would make the card not work right without the correct drive.

8 minutes ago, mnovak said:

Yes that's what I am running now. The suggestion of downgrading to the v530.41.03 so that the Steam Headless docker would work might not work with the 4060 Ti that I have.

5 minutes ago, HellraiserOSU said:

Yes that's what I am running now. The suggestion of downgrading to the v530.41.03 so that the Steam Headless docker would work might not work with the 4060 Ti that I have.

Kindly read the last line of drivers for the 4060ti