New Dockers available

[jusjoken]

New dockers now available in Unraid and Docker Hub for SageTV and OpenDCT with a number of options included.

Change log here...

Thanks to Stuckless for the original foundational work on these as well as other users such as Madz whom I borrowed some updates from and Hvymetal for other inspiration to pull this together.

Setting your own hostname for a docker

Github source
Docker Hub link
Unraid template source

[jusjoken]

More pics

[jusjoken]

Change Log

### 2.0.5
- ServerJ11 - moved JDK from 11.0.2 to 11.0.15 to resolve TLS 1.3 error
- Note: other dockers were not changed
### 2.0.4
- ODCT - now uses ubuntu 20.04
- ODCT - removed changing properties to force media server as that is the default anyway
### 2.0.3
- ODCT - exposed ports 9091 and 8271
### 2.0.2
- ServerODCTJ11 - fix to path for JVM
- ServerODCTJ16 - fix to path for JVM
- template changes for changelog, versioning and support link
### 2.0.1
- initial release: setup Docker Hub and Github repositories
- Server: change base os to ubuntu 20.04
- Server: fix gentuner and commandir old bintray links
- ServerJ8: fix to cacert issue blocking placeshifter connection
- ServerODCT: add 8,11,16 containers embedding OpenDCT
- Server: fix to get latest SageTV release from Github
- ServerODCT: fix to get latest SageTV/OpenDCT releases from Github
- ODCT: update to get latest ODCT release from Github
- Templates: update to support all new containers
- BuildScripts: updated to include all containers

[KeithAbbott]

Wow, it looks like Christmas came a couple of weeks late this year! So if I want to try this out before I decide to fully migrate, can I stop my stuckless-sagetv-server-java11 and crazifuzzy-opendct dockers, install the sagetvopen-sagetv-server-opendct-java11 and start it up? Then, to switch back to my existing docker(s), I just stop the new docker and start the old ones back up. Is it that simple, or is it more complicated than that?

Also, if I am currently using the stuckless-sagetv-server-java11 docker, does it make sense for me to stick with your sagetvopen-sagetv-server-opendct-java11 docker? I had tried Sean's java16 docker, but some of the web UI was not functioning properly.

[jusjoken]

Originally Posted by KeithAbbott

Wow, it looks like Christmas came a couple of weeks late this year! So if I want to try this out before I decide to fully migrate, can I stop my stuckless-sagetv-server-java11 and crazifuzzy-opendct dockers, install the sagetvopen-sagetv-server-opendct-java11 and start it up? Then, to switch back to my existing docker(s), I just stop the new docker and start the old ones back up. Is it that simple, or is it more complicated than that?

Also, if I am currently using the stuckless-sagetv-server-java11 docker, does it make sense for me to stick with your sagetvopen-sagetv-server-opendct-java11 docker? I had tried Sean's java16 docker, but some of the web UI was not functioning properly.

Yes that will work. I run sometimes 4 or 5 SageTV dockers at a time for testing. In the template I change Host to br0 and set an unused IP and then I change the appdata path to something different so it doesn't touch my prod docker data...then start it up...even with the prod one running.

K

[technazz]

Thanks

Might want to update the links for the Support Link in the Unraid Docker.

I see there is an update to the docker. Is there a changelog I can see prior to updating?

Thx!

[KeithAbbott]

Originally Posted by jusjoken

Yes that will work. I run sometimes 4 or 5 SageTV dockers at a time for testing. In the template I change Host to br0 and set an unused IP and then I change the appdata path to something different so it doesn't touch my prod docker data...then start it up...even with the prod one running.

K

So I would change the appdata path from /mnt/user/appdata/sagetv/ to something like /mnt/user/appdata/sagetv-opendct/, correct? Does that directory need to exist before starting the docker, or will it create it automatically?

Also, if I am currently running the crazifuzzy-opendct docker for my production SageTV instance, will your docker play nicely with it since both dockers seem to be pointing to the same configuration, log and home paths? Both dockers can be running simultaneously?