Can you run multiple SageTV Dockers on one unRAID server?

[wayner]

As long as you are careful to use a different docker name, different ports, and different appdata folders, can you run multiple SageTV server docker instances on the same server? This could be useful to try out configuration changes, new versions, etc without having to bring down the system for the rest of the family.

[stuckless]

Originally Posted by wayner

As long as you are careful to use a different docker name, different ports, and different appdata folders, can you run multiple SageTV server docker instances on the same server? This could be useful to try out configuration changes, new versions, etc without having to bring down the system for the rest of the family.

You can, but it will be challenging. You will need to reconfigure all the internal ports, which I think will be a bit of work.

[Fuzzy]

Originally Posted by stuckless

You can, but it will be challenging. You will need to reconfigure all the internal ports, which I think will be a bit of work.

I believe unRAID 6.4 (in beta currently) uses macvlan for the docker interfaces, allowing individual containers to have their own IP address on the network if desired, in which case, each of the 'servers' can be their own 'system', thus preventing port issues. You would still need different appdata folders for each though.

[wayner]

Originally Posted by Fuzzy

I believe unRAID 6.4 (in beta currently) uses macvlan for the docker interfaces, allowing individual containers to have their own IP address on the network if desired, in which case, each of the 'servers' can be their own 'system', thus preventing port issues. You would still need different appdata folders for each though.

You're right Fuzzy it does - I have been following some of the threads on the unRAID forums. That will make this a lot easier. I think I will use that feature by default in the future as I find it easier to keep track of IP addresses then to be using all kinds of funky port numbers.

[wayner]

Which ports do I need to be worried about?

Would it be all of the ones in the Docker start command, as in:

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="stuckless-sagetv-server-java8" --net="host" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "VERSION"="latest" -e "JAVA_MEM_MB"="3072" -e "LICENCE_DATA"="" -e "TCP_PORT_7070"="7070" -e "TCP_PORT_42024"="42024" -e "TCP_PORT_7818"="7818" -e "UDP_PORT_8270"="8270" -e "UDP_PORT_31100"="31100" -e "TCP_PORT_31099"="31099" -e "UDP_PORT_16867"="16867" -e "UDP_PORT_16869"="16869" -e "TCP_PORT_16881"="16881" -e "OPT_GENTUNER"="Y" -e "OPT_COMMANDIR"="N" -e "OPT_COMSKIP"="Y" -e "OPT_SETPERMS"="Y" -e "OPT_LIRC"="N" -v "/mnt/user/appdata/sagetv/":"/opt/sagetv":rw -v "/mnt/user/media/":"/var/media":rw -v "/mnt/user/media2/videos/":"/var/mediaext":rw -v "/mnt/user":"/unraid":rw stuckless/sagetv-server-java8

[Fuzzy]

Those are, for the most part, the ports that sage uses. The issue is that anything that connects to those ports - network encoders, clients, placeshifter, etc - all ALSO need to know what ports you change them too. So much so, that it really is not likely worth it, and if you genuinely want to run a second server for some reason, it might be wise to separate it to a different IP instead. Whether that's running it in a VM that has a different IP address, or upgrading to the prerelease 6.4.x of unRAID to get the new network stack for docker that would allow it to - Or wait for 6.4 to be brought to release.