March 1, 20233 yr 10 hours ago, patrickstigler said: Hi Sorry for the delay. I will take a look at it, but currently I am quite busy so I had no time to do something on the image. Also my network interface broke (might be a software issue) but now I have to fix the build pipeline first. I will update you guys here. Thank you!
March 12, 20233 yr On 3/1/2023 at 5:37 AM, patrickstigler said: Hi Sorry for the delay. I will take a look at it, but currently I am quite busy so I had no time to do something on the image. Also my network interface broke (might be a software issue) but now I have to fix the build pipeline first. I will update you guys here. No need to be sorry, I'm just grateful for your work
March 21, 20233 yr Hi gents, Waited a bit to work on fixing this myself and ended up revamping a bit of it back to the old system to get it to work. The new accetto/ubuntu vnc based image does not play well with avahi so NDI is unable to locate sources. I've posted the changes to: https://github.com/mountaintopsolutions/docker-obs-ndi-ng The summary is: Went back to the old container format for now. based on the old images when this was first published. Updated to ubuntu 22.04 Updated OBS to 29.0.2 Updated NDI plugin Fixed startup scripts. The images are available for the unraid OBS-NDI plugin at https://hub.docker.com/r/mountaintopsolutions/docker-obs-ndi-ng they can be imported by changing the repository URL for the OBS-NDI image to: mountaintopsolutions/docker-obs-ndi-ng:legacy-latest or if you want to stay safe and not get any updates mountaintopsolutions/docker-obs-ndi-ng:legacy-1.0 This container uses port 5900 for direct VNC connections and 5901 for novnc connections. Please let me know if you have any problems or suggestions. for the "NG" part of docker-obs-ndi-ng I have rebuilt the accetto based image, fixed the issues, and have it running manually but it needs some startup script changes that will require rebuilding the entire accetto base image to fix, as avahi and dbus need to start with xvnc. When i have time to fix that I will publish those images, but this should get everyone back streaming for now. -- DC Screenshot attached showing we are cooking with gas again!
March 24, 20233 yr Im not sure where else to post this... Im hoping Im in the right place. I am trying to manage the settings and it is asking for my GPU name. So far I have been unable to find an acceptable name for the setting and it keeps failing on me. Where do I find this name in the correct format? Edit.. I have an Nvidia GPU so Im assuming I have to use this. Edited March 24, 20233 yr by Haytar
March 24, 20233 yr Ok.. got it working but it doesnt seem to have NDI installed when I open the interface? I am very confused now.
March 24, 20233 yr Ok I havent figured out how to delete my own posts. I have figured out more and more as I post so ... sorry bout the stacking posts. But... I have since installed the version linked in the post before my first post... but it just stays on "started" or w/e and I can't access its web interface.
March 24, 20233 yr The web interface is on port 5901, the latest template says 6901, if you try http://ip:5901 it should give you the novnc interface. you can also connect directly with your own vnc client on port 5900 To delete a post click the ... on the post header and click delete. Edited March 24, 20233 yr by mountaintop
March 25, 20233 yr 9 hours ago, Haytar said: Ok.. got it working but it doesnt seem to have NDI installed when I open the interface? I am very confused now. I too am missing the NDI stuff in the latest container! This is a new instal. I used it before, and everything worked great (i just had a useless PC to stream from before now). Edited March 25, 20233 yr by miicar
March 27, 20233 yr On 3/24/2023 at 10:07 PM, miicar said: I too am missing the NDI stuff in the latest container! This is a new instal. I used it before, and everything worked great (i just had a useless PC to stream from before now). Instructions above in the post linked for a fixed container image: https://forums.unraid.net/topic/114911-support-obs-ndi/?do=findComment&comment=1242303
March 27, 20233 yr On 3/21/2023 at 1:26 AM, mountaintop said: Hi gents, Waited a bit to work on fixing this myself and ended up revamping a bit of it back to the old system to get it to work. The new accetto/ubuntu vnc based image does not play well with avahi so NDI is unable to locate sources. I've posted the changes to: https://github.com/mountaintopsolutions/docker-obs-ndi-ng The summary is: Went back to the old container format for now. based on the old images when this was first published. Updated to ubuntu 22.04 Updated OBS to 29.0.2 Updated NDI plugin Fixed startup scripts. The images are available for the unraid OBS-NDI plugin at https://hub.docker.com/r/mountaintopsolutions/docker-obs-ndi-ng they can be imported by changing the repository URL for the OBS-NDI image to: mountaintopsolutions/docker-obs-ndi-ng:legacy-latest or if you want to stay safe and not get any updates mountaintopsolutions/docker-obs-ndi-ng:legacy-1.0 This container uses port 5900 for direct VNC connections and 5901 for novnc connections. Please let me know if you have any problems or suggestions. for the "NG" part of docker-obs-ndi-ng I have rebuilt the accetto based image, fixed the issues, and have it running manually but it needs some startup script changes that will require rebuilding the entire accetto base image to fix, as avahi and dbus need to start with xvnc. When i have time to fix that I will publish those images, but this should get everyone back streaming for now. -- DC Screenshot attached showing we are cooking with gas again! Hi, I have it up and running but i cant find any "Source name" When i set up VM win10 and install it works fine but i can´t get it to work with the Docker. /Johan
March 27, 20233 yr Johan, I just tested again on a fresh container and after making sure my OBS was open on my gaming PC it shows up on the drop down list as a source as it should. Did you give the docker container an IP as thought its another device on your network? (IE: i uses 192.168.1.x and my docker container has an IP of 192.168.1.250) or does it have a docker assigned IP like 172.16.x.x? If its the docker assigned IP, change to using your bridge device (br0 most likely) for networking and give it a normal IP on your network and the problem should be resolved. The NDI plugin uses avahi / mdns to broadcast service availability, make sure that nothing is blocking communication. (firewall, having docker container on a different LAN segment, using docker internal IP instead of bridged networking will all cause avahi not to work.) Edited March 27, 20233 yr by mountaintop
March 28, 20233 yr 10 hours ago, mountaintop said: Johan, I just tested again on a fresh container and after making sure my OBS was open on my gaming PC it shows up on the drop down list as a source as it should. Did you give the docker container an IP as thought its another device on your network? (IE: i uses 192.168.1.x and my docker container has an IP of 192.168.1.250) or does it have a docker assigned IP like 172.16.x.x? If its the docker assigned IP, change to using your bridge device (br0 most likely) for networking and give it a normal IP on your network and the problem should be resolved. The NDI plugin uses avahi / mdns to broadcast service availability, make sure that nothing is blocking communication. (firewall, having docker container on a different LAN segment, using docker internal IP instead of bridged networking will all cause avahi not to work.) Don´t realy know how but now it works. Did change device for network so i got like 172.16.x.x and then i changed back to br0 and now it works fine:)
April 2, 20233 yr Hi new question, Is it possible to transfer for example pictures to the docker? So if the game PC reboot you still get a picture instead of the black screen.
May 1, 20233 yr On 3/20/2023 at 8:26 PM, mountaintop said: Hi gents, Waited a bit to work on fixing this myself and ended up revamping a bit of it back to the old system to get it to work. The new accetto/ubuntu vnc based image does not play well with avahi so NDI is unable to locate sources. I've posted the changes to: https://github.com/mountaintopsolutions/docker-obs-ndi-ng The summary is: Went back to the old container format for now. based on the old images when this was first published. Updated to ubuntu 22.04 Updated OBS to 29.0.2 Updated NDI plugin Fixed startup scripts. The images are available for the unraid OBS-NDI plugin at https://hub.docker.com/r/mountaintopsolutions/docker-obs-ndi-ng they can be imported by changing the repository URL for the OBS-NDI image to: mountaintopsolutions/docker-obs-ndi-ng:legacy-latest or if you want to stay safe and not get any updates mountaintopsolutions/docker-obs-ndi-ng:legacy-1.0 This container uses port 5900 for direct VNC connections and 5901 for novnc connections. Please let me know if you have any problems or suggestions. for the "NG" part of docker-obs-ndi-ng I have rebuilt the accetto based image, fixed the issues, and have it running manually but it needs some startup script changes that will require rebuilding the entire accetto base image to fix, as avahi and dbus need to start with xvnc. When i have time to fix that I will publish those images, but this should get everyone back streaming for now. -- DC Screenshot attached showing we are cooking with gas again! I don't use Unraid but I wanted to come her to say THANK YOU! Because of your work I can now use my NAS to stream. I use Openmediavault instead of Unraid and I was able to use your container in Portainer to stream from my gaming computer to the OBS on my NAS thanks to you. Just have to find why my frames are topping out at 43fps on my server and how to implement QSV. Thanks again. Also, if anyone doesn't have anything in their NDI source, use this vid: Essentially you are setting up a Config network and your own MacVLAN network to attach to the OBS container. I also had to use MyIP:5901 to access. The port had to be in the URL.
May 2, 20233 yr Hi @mountaintop, Thanks for getting this back up and running. Just a quick question, any idea how to enable hardware decoding for NVIDIA. Encoding seems to work fine but for some reason I cannot get OBS to hardware decode an SRT media source. It works on OBS in windows, not sure if this is a linux issue or if there is something else I need to add to the docker image. Cheers
May 22, 20233 yr On 3/27/2023 at 4:24 PM, mountaintop said: Johan, I just tested again on a fresh container and after making sure my OBS was open on my gaming PC it shows up on the drop down list as a source as it should. Did you give the docker container an IP as thought its another device on your network? (IE: i uses 192.168.1.x and my docker container has an IP of 192.168.1.250) or does it have a docker assigned IP like 172.16.x.x? If its the docker assigned IP, change to using your bridge device (br0 most likely) for networking and give it a normal IP on your network and the problem should be resolved. The NDI plugin uses avahi / mdns to broadcast service availability, make sure that nothing is blocking communication. (firewall, having docker container on a different LAN segment, using docker internal IP instead of bridged networking will all cause avahi not to work.) I'm just now having the same issue he described. I've installed the same version of OBS and the NDI dependencies on my main PC to match what's in the docker image, but I'm only able to see the Preview output. As far as I can tell, that does not actually send any audio either. I've set up a firewall exemption for OBS on my PC, and I've made sure that br0 is the docker's network adapter.
November 7, 20232 yr Someone got it working with intel arc? I put the mentioned paramaters in but intel_gpu_top showing nothing.
October 20, 20241 yr I can' get mine to launch. I guess it can't set itself up because permissions are denied? Not sure what's going on here, since I can even set full permissions to the folders themselves but it never has permission to do anything... All my other docker containers have had no issues like this. mkdir: cannot create directory '/home/headless/.vnc': Permission denied /dockerstartup/vnc_startup.rc: line 57: /home/headless/.vnc/passwd: No such file or directory chmod: cannot access '/home/headless/.vnc/passwd': No such file or directory /dockerstartup/vnc_startup.rc: line 65: /home/headless/.vnc/config: No such file or directory /dockerstartup/vnc_startup.rc: line 99: /dockerstartup/vnc.log: Permission denied /dockerstartup/vnc_startup.rc: line 127: /dockerstartup/novnc.log: Permission denied /dockerstartup/startup.sh: line 25: kill: (25) - No such process
December 3, 20241 yr On 10/20/2024 at 11:38 AM, oxideSeven said: I can' get mine to launch. I guess it can't set itself up because permissions are denied? Not sure what's going on here, since I can even set full permissions to the folders themselves but it never has permission to do anything... All my other docker containers have had no issues like this. mkdir: cannot create directory '/home/headless/.vnc': Permission denied /dockerstartup/vnc_startup.rc: line 57: /home/headless/.vnc/passwd: No such file or directory chmod: cannot access '/home/headless/.vnc/passwd': No such file or directory /dockerstartup/vnc_startup.rc: line 65: /home/headless/.vnc/config: No such file or directory /dockerstartup/vnc_startup.rc: line 99: /dockerstartup/vnc.log: Permission denied /dockerstartup/vnc_startup.rc: line 127: /dockerstartup/novnc.log: Permission denied /dockerstartup/startup.sh: line 25: kill: (25) - No such process same here
February 5, 20251 yr On 10/20/2024 at 5:38 PM, oxideSeven said: I can' get mine to launch. I guess it can't set itself up because permissions are denied? Not sure what's going on here, since I can even set full permissions to the folders themselves but it never has permission to do anything... All my other docker containers have had no issues like this. mkdir: cannot create directory '/home/headless/.vnc': Permission denied /dockerstartup/vnc_startup.rc: line 57: /home/headless/.vnc/passwd: No such file or directory chmod: cannot access '/home/headless/.vnc/passwd': No such file or directory /dockerstartup/vnc_startup.rc: line 65: /home/headless/.vnc/config: No such file or directory /dockerstartup/vnc_startup.rc: line 99: /dockerstartup/vnc.log: Permission denied /dockerstartup/vnc_startup.rc: line 127: /dockerstartup/novnc.log: Permission denied /dockerstartup/startup.sh: line 25: kill: (25) - No such process same here
March 6, 20251 yr Hi, testing to use the OBS-NDI docker to stream from my main PC to and use my server that has an Quadro P2200 to utilize the nvenc to stream to twitch i have got it to work and i can see in nvidia-SMI that it is using the gpu but its also using about 60% all core load on my xeon E5-2470v2 is that normal ? this is while the docker is running and havent even started the stream only seeing the viewfinder that it is streaming the content over the lan seems very strange that it uses this much CPU on the server with the NDI link ?
March 7, 20251 yr On 3/20/2023 at 6:26 PM, mountaintop said: Hi gents, Waited a bit to work on fixing this myself and ended up revamping a bit of it back to the old system to get it to work. The new accetto/ubuntu vnc based image does not play well with avahi so NDI is unable to locate sources. I've posted the changes to: https://github.com/mountaintopsolutions/docker-obs-ndi-ng The summary is: Went back to the old container format for now. based on the old images when this was first published. Updated to ubuntu 22.04 Updated OBS to 29.0.2 Updated NDI plugin Fixed startup scripts. The images are available for the unraid OBS-NDI plugin at https://hub.docker.com/r/mountaintopsolutions/docker-obs-ndi-ng they can be imported by changing the repository URL for the OBS-NDI image to: mountaintopsolutions/docker-obs-ndi-ng:legacy-latest or if you want to stay safe and not get any updates mountaintopsolutions/docker-obs-ndi-ng:legacy-1.0 This container uses port 5900 for direct VNC connections and 5901 for novnc connections. Please let me know if you have any problems or suggestions. for the "NG" part of docker-obs-ndi-ng I have rebuilt the accetto based image, fixed the issues, and have it running manually but it needs some startup script changes that will require rebuilding the entire accetto base image to fix, as avahi and dbus need to start with xvnc. When i have time to fix that I will publish those images, but this should get everyone back streaming for now. -- DC Screenshot attached showing we are cooking with gas again! I just set up your container and everything worked perfectly right off the bat! Would it be possible to add a "spice" option along side VNC for accessing the container? Spice allows for usb passthrough, so we could use stream decks and foot pedals to control the OBS scenes in the container. It's not necessary by any means, but it would be a nice quality of life upgrade. I'm not too familiar with containerization, but I would be happy to help in any way that I can!
August 21, 2025Aug 21 It won't start.mkdir: cannot create directory '/home/headless/.vnc': Permission denied/dockerstartup/vnc_startup.rc: line 57: /home/headless/.vnc/passwd: No such file or directorychmod: cannot access '/home/headless/.vnc/passwd': No such file or directory/dockerstartup/vnc_startup.rc: line 65: /home/headless/.vnc/config: No such file or directory/dockerstartup/vnc_startup.rc: line 99: /dockerstartup/vnc.log: Permission denied/dockerstartup/vnc_startup.rc: line 127: /dockerstartup/novnc.log: Permission denied/dockerstartup/startup.sh: line 25: kill: (19) - No such processAnd does it support intel? Added dev/dri, but can't start it because it lacks permissions. Also set it to privileged, and added path for configs to be in, but no permissions.
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.