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!

[jusjoken]

Originally Posted by 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!

I have a change log on my todo list and will try to post here as well. Part of the change was to build a process so each docker change will cause an update notice but for those interested I will create a technical post outlining what I did to get these new dockers published

But keep in mind, these dockers do not change SageTV nor openDCT...they just install the current posted versions inside.

Hope that helps for now.

K

[wayner]

If I wanted to add opendct to an existing docker could I just change the repository name, assuming that I am using the same Java version?

[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?

[jusjoken]

Originally Posted by KeithAbbott

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?

Correct, and if it does not exist then unraid will create it. It could just be something like: /mnt/user/appdata/sagetv2/. Keep in mind, this path is where the SageTV part of the install will be located (not the opendct part...see below).

Originally Posted by KeithAbbott

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?

The opendct paths in the config need to point to the appdata paths you want the opendct part of the install to be located (3 paths). If you leave them at the default which is the same as the separate opendct container then it will overwrite (perhaps conflict) with the other container.

* perhaps I should change these defaults so they do not conflict...I will review in future docker releases

Note: I do not use opendct so cannot really comment on if the 2 containers would conflict but my gut would say they should at minimum have a different appdata path (for all 3 path settings) like I suggested for SageTV.

Example...



Hope that helps

K

[jusjoken]

Originally Posted by wayner

If I wanted to add opendct to an existing docker could I just change the repository name, assuming that I am using the same Java version?

I don't think I would as the template would not have all the opendct settings (paths).

I would tend to stop the existing dockers (turn off autostart too) then go to apps and select the new combined docker and when configuring it just point it to the same sagetv and opendct paths as the 2 previous dockers used (making sure you had a backup just in case).

Then start the new docker...and if all is good, do a remove on the old dockers.

Hope that helps.

K

[KeithAbbott]

Originally Posted by jusjoken

I don't think I would as the template would not have all the opendct settings (paths).

I would tend to stop the existing dockers (turn off autostart too) then go to apps and select the new combined docker and when configuring it just point it to the same sagetv and opendct paths as the 2 previous dockers used (making sure you had a backup just in case).

Then start the new docker...and if all is good, do a remove on the old dockers.

Hope that helps.

K

Following these steps, the new combined docker would utilize the existing sage.properties and wiz.bin properties, correct? Would existing plugins just work, or would they need to be re-installed?

[jusjoken]

Originally Posted by KeithAbbott

Following these steps, the new combined docker would utilize the existing sage.properties and wiz.bin properties, correct? Would existing plugins just work, or would they need to be re-installed?

Correct. No change to plugins needed. Inside the docker it sees no change.

K

[KeithAbbott]

I'm trying to get sagetvopen-sagetv-server-opendct-java11 docker going as a test environment, but I am running into an issue. From what I can tell, OpenDCT is unable to start the JVM. SageTV appears to successfully start, although without tuners it doesn't do much good. However, it does playback previously recorded shows without an issue. I've attached the log file.

[jusjoken]

Originally Posted by KeithAbbott

I'm trying to get sagetvopen-sagetv-server-opendct-java11 docker going as a test environment, but I am running into an issue. From what I can tell, OpenDCT is unable to start the JVM. SageTV appears to successfully start, although without tuners it doesn't do much good. However, it does playback previously recorded shows without an issue. I've attached the log file.

I have an idea what the problem might be. There is a part in the Java 8 docker that is not part of the 11 and 16. I will review tomorrow morning and see how to resolve.

If you want you could change the 11 to and 8 in the docker registry name and apply and it will load the Java 8 docker instead to see if it makes a difference

K

[jusjoken]

Originally Posted by KeithAbbott

I'm trying to get sagetvopen-sagetv-server-opendct-java11 docker going as a test environment, but I am running into an issue. From what I can tell, OpenDCT is unable to start the JVM. SageTV appears to successfully start, although without tuners it doesn't do much good. However, it does playback previously recorded shows without an issue. I've attached the log file.

This should now be resolved. Use the force update option on the docker in unraid and it should pull the new docker and load OpenDCT within the container properly.

Let me know how it goes.

K

[jusjoken]

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]

Originally Posted by jusjoken

This should now be resolved. Use the force update option on the docker in unraid and it should pull the new docker and load OpenDCT within the container properly.

Let me know how it goes.

K

It appears to be working now, I was able to add one of my HDHR Prime tuners, and am able to view live channels. Since it is a test environment, I ran into a tuner locking issue with the HDHRs, so I had to shut down my production environment temporarily to successfully test. I think that is just a properties setting in OpenDCT, if I really wanted to maintain a test environment I would spend time chasing it down. I am a bit surprised, it didn't find any of my HDHR OTA tuners, but I'm also not going to spend much time figuring that out either.

I'll probably look for an opportunity to do the in-place upgrade that you described earlier, which should retain all of my tuners, channel lineups, plugins, etc.

[KeithAbbott]

Originally Posted by jusjoken

I would tend to stop the existing dockers (turn off autostart too) then go to apps and select the new combined docker and when configuring it just point it to the same sagetv and opendct paths as the 2 previous dockers used (making sure you had a backup just in case).

Then start the new docker...and if all is good, do a remove on the old dockers.

Hope that helps.

K

No doubt I would take a backup of appdata prior to switching over to the new combined docker, as described above. If things really went haywire, I could restore from the appdata backup. But I am curious: instead of restoring from the backup, could I just reverse the steps and revert back to the existing stuckless and crazifuzzy dockers?

[jusjoken]

Originally Posted by KeithAbbott

No doubt I would take a backup of appdata prior to switching over to the new combined docker, as described above. If things really went haywire, I could restore from the appdata backup. But I am curious: instead of restoring from the backup, could I just reverse the steps and revert back to the existing stuckless and crazifuzzy dockers?

Sure...and likely pointing them back at the copy of appdata folders prior to your test. The copy is entirely a safety net that I always do and recommend but I often for testing purposes completely setup a test system with tuners and plugins and then copy the appdata folders and point another docker at the copy so I can skip the configuration step.

Just keep in mind that there is really no data in the docker... The dockers point to data outside of the docker. The difference inside the docker is OS and Java versions, defaults, etc. But the new docker could change data in the appdata folder like a default property etc that we may need to review and fix. Hence the copy and test. But I think the potential is low. Sage and opendct should see an already configured system and just use that configuration
K