New docker templates - Work in Progress

[jusjoken]

I have created a new Github location under OpenSageTV and have updated a number of the stuckless dockers and templates in order to resolve a few issues, make them more current and more maintainable.

These have recently been made available as well under the Community Applications app on Unraid.

This is a work in progress so these dockers will be under construction and changing over the coming days/weeks but so far the Java 11 one seems the most stable.

I will post more on this and update the support thread with current instructions as I move forward with this work.

K

[wayner]

Thanks Ken - awesome stuff!

[wayner]

I see that there is an update available already. What was updated?

[jusjoken]

Originally Posted by wayner

I see that there is an update available already. What was updated?

I fixed gentuner and commandir

K.

[jusjoken]

I have updated all 3 dockers available within unraid under sagetvopen

All 3 now use ubuntu 20.04 internally

Java 8 docker seems to work now since the latest 9.2.7 linux build that resolved some Java 8 specific issues

Java 11 docker still seems solid

Java 16 works well except does not yet support some of the Jetty Web pages. Work in progress to determine how to resolve.

K

[hvymetal]

@jusjoken Thanks for updating the SageTV dockers. I noticed you also connected to crazifuzzy-opendct to the new repository. The docker is still broken because it using old URL to bintray. See log below. I have resorted to installing OpenDCT directly inside the SageTV docker.

Dload Upload Total Spent Left Speed
Installing OpenDCT ...
--2022-01-05 09:42:22-- https://dl.bintray.com/opendct/Releases/releases//opendct_-1_amd64.deb
Resolving dl.bintray.com (dl.bintray.com)... 54.70.2.80, 52.39.229.247
Connecting to dl.bintray.com (dl.bintray.com)|54.70.2.80|:443... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2022-01-05 09:42:22 ERROR 502: Bad Gateway.


dpkg-deb: error: 'opendct_-1_amd64.deb' is not a debian format archive

dpkg: error processing archive opendct_-1_amd64.deb (--install):

subprocess dpkg-deb --control returned error exit status 2

[wayner]

edit - This is on Java 11

I seem to have an issue with 9.2.7.1. I tried restarting my docker this morning and it appears to have upgraded from 9.2.6.1 to 9.2.7.1. I can't access Sage via either the web UI or Placeshifter.

It seems that when Sage tries to detect Capture devices it craps out on my HDHR.

Is it possible to roll back to version 9.2.6.1?

In all of my sagetv_X.txt log files I see:

Wed 1/5 8:59:01.814 [main@3567135c] MMC calling detectCaptureDevices on sage.HDHomeRunCaptureManager@68c9133c
Wed 1/5 8:59:01.814 [main@3567135c] MAIN THREW AN EXCEPTION: java.lang.UnsatisfiedLinkError: sage.HDHomeRunCaptureManager.getDeviceList0()[Ljava/lang/String;
Wed 1/5 8:59:01.815 [main@3567135c] java.lang.UnsatisfiedLinkError: sage.HDHomeRunCaptureManager.getDeviceList0()[Ljava/lang/String;
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.HDHomeRunCaptureManager.getDeviceList0(Native Method)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.HDHomeRunCaptureManager.detectCaptureDevices(HDHomeRunCaptureManager.java:62)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.MMC.init(MMC.java:89)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.MMC.prime(MMC.java:65)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.SageTV.<init>(SageTV.java:410)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.Sage.startup(Sage.java:1172)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.Sage.main(Sage.java:952)
Wed 1/5 8:59:01.815 [main@3567135c] Exception in thread "main" Wed 1/5 8:59:01.815 [main@3567135c] java.lang.UnsatisfiedLinkError: sage.HDHomeRunCaptureManager.getDeviceList0()[Ljava/lang/String;
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.HDHomeRunCaptureManager.getDeviceList0(Native Method)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.HDHomeRunCaptureManager.detectCaptureDevices(HDHomeRunCaptureManager.java:62)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.MMC.init(MMC.java:89)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.MMC.prime(MMC.java:65)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.SageTV.<init>(SageTV.java:410)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.Sage.startup(Sage.java:1172)
Wed 1/5 8:59:01.815 [main@3567135c] 	at sage.Sage.main(Sage.java:952)

My docker log doesn't have much of interest.

*** Running /etc/my_init.d/20-upgrade-sagetv...
SageTV Home: /opt/sagetv/server
Finding latest stable version...
9.2.7.1 is the lastest matching version on OpenSageTV/sagetv-linux
Finding download URL for version 9.2.7.1...
SageTV Server binary (.tar.gz) for 9.2.7.1 can be installed from https://github.com/OpenSageTV/sagetv-linux/releases/download/9.2.7.1/sagetv-server_9.2.7_amd64.tar.gz
SageTV Already At Version: 9.2.7.1, exiting...
*** Running /etc/my_init.d/25-add-license...
*** Running /etc/my_init.d/25-sagetv-docker-env...
Updating Java Mem 2500
*** Running /etc/my_init.d/25-upgrade-commandir...
*** Running /etc/my_init.d/25-upgrade-comskip...
Comskip already installed
*** Running /etc/my_init.d/25-upgrade-gentuner...
Generic Tuner Plugin already installed
*** Running /etc/my_init.d/30-setperms...
*** Running /etc/my_init.d/40-lirc...
mode of '/usr/bin/irsend' changed from 0755 (rwxr-xr-x) to 4755 (rwsr-xr-x)
*** Running /etc/my_init.d/85-user-script...
*** Running /etc/my_init.d/90-sagetv...
Changing to SageTV directory /opt/sagetv/server
Executing pre-scripts
*** Running /etc/my_init.d/95-jstatd...
JSTATD Remote Java Debugging is disabled.
*** Running /etc/my_init.d/99-zmessage...

************************************************
SageTV unRAID/Docker (Container Version: 1.1.0) is running
If this is your first time, install the Windows/Mac/Linux Placeshifter or the Android MiniClient and complete the configuration
Setting up tuners, scheduling recordings, installing plugins, etc, requires using the Placeshifter or MiniClient
To gain browser access, install the Jetty WebServer Plugin
- The SageTV Team -
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 92
Jan 5 16:18:04 120ca6c882ca cron[95]: (CRON) INFO (pidfile fd = 3)
Jan 5 16:18:04 120ca6c882ca cron[95]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
Starting server mode
Main is starting

[hvymetal]

Originally Posted by wayner

edit - This is on Java 11

I seem to have an issue with 9.2.7.1. I tried restarting my docker this morning and it appears to have upgraded from 9.2.6.1 to 9.2.7.1. I can't access Sage via either the web UI or Placeshifter.

It seems that when Sage tries to detect Capture devices it craps out on my HDHR.

Is it possible to roll back to version 9.2.6.1?

Originally Posted by hvymetal

With version 9.2.7 above this will break current docker cofinguartions because the older dockers were using ubuntu 18.04 that has an older GLIBC required for the newer build to run. GBLIC is not easy to upgrade with replacing OS. There are two options:

1. Fix the version in the docker to template to 9.2.6.1
2. Use an updated docker template created by jusjoken

https://forums.sagetv.com/forums/showthread.php?t=66879

Also next Post will have updated steps as the update script is not longer needed if new template is used.

https://forums.sagetv.com/forums/sho...31&postcount=9

[wayner]

Thanks. Regarding fix # 1, how do you change the docker to use 9.2.6.1 - can we do that ourselves? Or do we need Jusjoken to do that?

Regarding fix #2, I am using the new updated docker template the jusjoken created. I am using sagetvopen/sagetv-server-java11 . Or is there now a newer one?

[jusjoken]

Originally Posted by hvymetal

@jusjoken Thanks for updating the SageTV dockers. I noticed you also connected to crazifuzzy-opendct to the new repository. The docker is still broken because it using old URL to bintray. See log below. I have resorted to installing OpenDCT directly inside the SageTV docker.

Dload Upload Total Spent Left Speed
Installing OpenDCT ...
--2022-01-05 09:42:22-- https://dl.bintray.com/opendct/Releases/releases//opendct_-1_amd64.deb
Resolving dl.bintray.com (dl.bintray.com)... 54.70.2.80, 52.39.229.247
Connecting to dl.bintray.com (dl.bintray.com)|54.70.2.80|:443... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2022-01-05 09:42:22 ERROR 502: Bad Gateway.


dpkg-deb: error: 'opendct_-1_amd64.deb' is not a debian format archive

dpkg: error processing archive opendct_-1_amd64.deb (--install):

subprocess dpkg-deb --control returned error exit status 2

Thanks for the note. I have not had time to review this but will and correct/update what I can.

K

[jusjoken]

Originally Posted by wayner

Thanks. Regarding fix # 1, how do you change the docker to use 9.2.6.1 - can we do that ourselves? Or do we need Jusjoken to do that?

Regarding fix #2, I am using the new updated docker template the jusjoken created. I am using sagetvopen/sagetv-server-java11 . Or is there now a newer one?

In unraid, stop your sagetvopen docker and then click force update. This will pull down the new docker that uses Ubuntu 20.04 and will work with Sagetv 9.2.7

K

[wayner]

Excellent - that worked. Thanks!

[jusjoken]

Originally Posted by hvymetal

@jusjoken Thanks for updating the SageTV dockers. I noticed you also connected to crazifuzzy-opendct to the new repository. The docker is still broken because it using old URL to bintray. See log below. I have resorted to installing OpenDCT directly inside the SageTV docker.

Dload Upload Total Spent Left Speed
Installing OpenDCT ...
--2022-01-05 09:42:22-- https://dl.bintray.com/opendct/Releases/releases//opendct_-1_amd64.deb
Resolving dl.bintray.com (dl.bintray.com)... 54.70.2.80, 52.39.229.247
Connecting to dl.bintray.com (dl.bintray.com)|54.70.2.80|:443... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2022-01-05 09:42:22 ERROR 502: Bad Gateway.


dpkg-deb: error: 'opendct_-1_amd64.deb' is not a debian format archive

dpkg: error processing archive opendct_-1_amd64.deb (--install):

subprocess dpkg-deb --control returned error exit status 2

I believe I fixed this. In unraid and on Docker Hub you will see a new docker under sagetvopen/opendct

This should contain fixes others have applied in the past and some other changes to clean things up.

However, I do not know how to test this. It runs but I only have an OTA HDHR and do not see any new sources when I try to configure sources. Perhaps this is normal as the OTA HDHR may not be supported and I have no other devices. Perhaps I am missing a post install step...not sure.

Can someone advise on my thinking above and if anyone can test out the updated docker please let me know the results.

K

[technazz]

Originally Posted by jusjoken

I believe I fixed this. In unraid and on Docker Hub you will see a new docker under sagetvopen/opendct

This should contain fixes others have applied in the past and some other changes to clean things up.

However, I do not know how to test this. It runs but I only have an OTA HDHR and do not see any new sources when I try to configure sources. Perhaps this is normal as the OTA HDHR may not be supported and I have no other devices. Perhaps I am missing a post install step...not sure.

Can someone advise on my thinking above and if anyone can test out the updated docker please let me know the results.

K

I use HDHR OTA through OpenDCT through a separate OpenDCT container though.

Do you have network discovery on in your Sage.properties?

network_encoder_discovery=true

[jusjoken]

Originally Posted by technazz

I use HDHR OTA through OpenDCT through a separate OpenDCT container though.

Do you have network discovery on in your Sage.properties?

network_encoder_discovery=true

I checked that setting and it is true (seems to be true on a new install).

I am using a separate OpenDCT container (separate from the SageTV container). Do I need to run the containers both in Host mode ? Currently I have each running as br0 with a different IP for each.

Any other thoughts ?

[jusjoken]

Originally Posted by jusjoken

I checked that setting and it is true (seems to be true on a new install).

I am using a separate OpenDCT container (separate from the SageTV container). Do I need to run the containers both in Host mode ? Currently I have each running as br0 with a different IP for each.

Any other thoughts ?

Nevermind...I got it working. I needed to restart the SageTV docker once the OpenDCT docker was running and that worked fine. I now see the tunners showing as "on sagetvopen-opendct".

So in theory users should be able to use this OpenDCT docker.

K

[technazz]

Originally Posted by jusjoken

Nevermind...I got it working. I needed to restart the SageTV docker once the OpenDCT docker was running and that worked fine. I now see the tunners showing as "on sagetvopen-opendct".

So in theory users should be able to use this OpenDCT docker.

K

Great Ill have to give it a try soon.
Thx

[jusjoken]

I should soon have a new docker with opendct included in the server docker.

I haven't determined yet if I will just make opendct an option in the current set of dockers or have a second set that include opendct...hmmm

K

[hvymetal]

Originally Posted by jusjoken

I should soon have a new docker with opendct included in the server docker.

I haven't determined yet if I will just make opendct an option in the current set of dockers or have a second set that include opendct...hmmm

K

Thanks for the fork of updating the docker images. My opinion is that since OpenDCT is only being used for SageTV why have it in a separate docker. Also having it in one docker guarantees that OpenDCT start first which is required for SageTV to find tuners. Why not but it as a template option?

[jusjoken]

Originally Posted by hvymetal

Thanks for the fork of updating the docker images. My opinion is that since OpenDCT is only being used for SageTV why have it in a separate docker. Also having it in one docker guarantees that OpenDCT start first which is required for SageTV to find tuners. Why not but it as a template option?

I agree... but I also like options so I think what I can do is update the docker build process I am using so when I build updated dockers it will just build the extra ones. So we would have dockers like...

sagetvopen/sagetv-opendct
sagetvopen/sagetv-server-java8
sagetvopen/sagetv-server-opendct-java8
sagetvopen/sagetv-server-java11
sagetvopen/sagetv-server-opendct-java11
sagetvopen/sagetv-server-java16
sagetvopen/sagetv-server-opendct-java16

That way users just pick the docker they want rather than searching for an option amongst all the other options that are typically just the default.

I will review the code needed to make this happen but likely easiest to support and may cause less confusion...but we will see

K