unofficial Docker Container for Record Engine
Re: unofficial Docker Container for Record Engine
Just tested the container on my new DS920+, works awesome just using the Docker package right from the third party section of the Package Center. I'll let you know if I have any issues or if anything comes up as I'm using it over the next few weeks.
Re: unofficial Docker Container for Record Engine
Nice work.
Given your container doesn't run with the privileged flag it really doesn't matter if it runs 'root' as it doesn't have privileged access. It only has access to the bind mounts (-v) nothing else.
Either way no harm running with custom PID/GID inside the container - however note the same PID/GID then need to reside on the docker host too. If on something like a synology that is royal PITA (as you discovered) - even just down to there is no way to create custom UID/GID from the synology UI
I was looking through your github repo, i was unclear if SD provide multiple architecture support in their package?
(i know your container is only amd64)
Given your container doesn't run with the privileged flag it really doesn't matter if it runs 'root' as it doesn't have privileged access. It only has access to the bind mounts (-v) nothing else.
Either way no harm running with custom PID/GID inside the container - however note the same PID/GID then need to reside on the docker host too. If on something like a synology that is royal PITA (as you discovered) - even just down to there is no way to create custom UID/GID from the synology UI
I was looking through your github repo, i was unclear if SD provide multiple architecture support in their package?
(i know your container is only amd64)
Re: unofficial Docker Container for Record Engine
Just because I don't mandate it doesn't mean someone can accidently set it and cause issues. so safer I think to change it.
You can from command line, just not from the UI.Either way no harm running with custom PID/GID inside the container - however note the same PID/GID then need to reside on the docker host too. If on something like a synology that is royal PITA (as you discovered) - even just down to there is no way to create custom UID/GID from the synology UI
There is nothing in the docker that is arch specific, so it would just be a matter of ensuring the right version of alpine linux is used as the baseline.I was looking through your github repo, i was unclear if SD provide multiple architecture support in their package?
(i know your container is only amd64)
The SD engine is a universal binary.
I'll look in to enabling arm as was curious about running on my Pi4 anyway..
-
- Posts: 101
- Joined: Wed May 27, 2015 9:15 am
- Device ID: 107BBE13, 10782AED
- Location: Madison, WI
- x 2
Re: unofficial Docker Container for Record Engine
I just loaded the most recent Synology SPK (HDHomeRunDVR-1.0.2.spk) and noticed that it is using Record Engine Version: 20200701, and yes, I have the BetaEngine flag set to 1.
I am also running this docker on my unRAID server, again with the BetaEngine flag set to 1, and it is using Record Engine Version: 20200521.
Here is the log from my unRAID server
I tried deleting hdhomerun_record from the /dvrdata directory to make sure there was not a problem deleting the old version, but no luck.
Is this expected? I was expecting the same version.
Thanks!
I am also running this docker on my unRAID server, again with the BetaEngine flag set to 1, and it is using Record Engine Version: 20200521.
Here is the log from my unRAID server
Code: Select all
** Validating the Config File is available and set up correctly
Config File exists and is writable - is record path and port correct
** Installing the HDHomeRunDVR Record Engine
Lets remove any existing engine - we're going to take the latest always....
Checking it was deleted - if we can't remove it we can't update
Downloading latest beta
Downloading latest release
Comparing which is newest
Both versions are same - using the Release version
Engine Updated to... 20200521
** Starting the DVR Engine
Is this expected? I was expecting the same version.
Thanks!
Re: unofficial Docker Container for Record Engine
Beta update doesn't work yet with the containerTBlankenheim wrote: ↑Sat Aug 08, 2020 8:13 pm I just loaded the most recent Synology SPK (HDHomeRunDVR-1.0.2.spk) and noticed that it is using Record Engine Version: 20200701, and yes, I have the BetaEngine flag set to 1.
I am also running this docker on my unRAID server, again with the BetaEngine flag set to 1, and it is using Record Engine Version: 20200521.
Here is the log from my unRAID serverI tried deleting hdhomerun_record from the /dvrdata directory to make sure there was not a problem deleting the old version, but no luck.Code: Select all
** Validating the Config File is available and set up correctly Config File exists and is writable - is record path and port correct ** Installing the HDHomeRunDVR Record Engine Lets remove any existing engine - we're going to take the latest always.... Checking it was deleted - if we can't remove it we can't update Downloading latest beta Downloading latest release Comparing which is newest Both versions are same - using the Release version Engine Updated to... 20200521 ** Starting the DVR Engine
Is this expected? I was expecting the same version.
Thanks!
Hope to work on an update this weekend
-
- Posts: 101
- Joined: Wed May 27, 2015 9:15 am
- Device ID: 107BBE13, 10782AED
- Location: Madison, WI
- x 2
Re: unofficial Docker Container for Record Engine
Not sure if this is important, but I noticed that the timestamp on hdhomerun_record looks to be the same as when the docker was started.Beta update doesn't work yet with the container
Hope to work on an update this weekend
If you are using the local timestamp to determine which file is newer, that could be a problem. From within the container, I did wget(s) of the record engine URL's and the retrieved files had current timestamps as opposed to the timestamp of the server file.
Hope this helps.
Re: unofficial Docker Container for Record Engine
the wget installed as part of busybox doesn't do the timestamping properly - that's the issue in the container right now.TBlankenheim wrote: ↑Sat Aug 08, 2020 9:10 pmNot sure if this is important, but I noticed that the timestamp on hdhomerun_record looks to be the same as when the docker was started.Beta update doesn't work yet with the container
Hope to work on an update this weekend
If you are using the local timestamp to determine which file is newer, that could be a problem. From within the container, I did wget(s) of the record engine URL's and the retrieved files had current timestamps as opposed to the timestamp of the server file.
Hope this helps.
using 'apt add wget' installs a usable version
I will be sure to add in the Dockerfile
I had thought to do a more complex version check using 'version' command on the downloaded record engines, but it's tricky to do in shell script.
Something for later maybe.
-
- Posts: 101
- Joined: Wed May 27, 2015 9:15 am
- Device ID: 107BBE13, 10782AED
- Location: Madison, WI
- x 2
Re: unofficial Docker Container for Record Engine
Is this something I should be able to do in the current container? Doesn't look like apt is a supported command unless I'm missing something obvious.using 'apt add wget' installs a usable version
Re: unofficial Docker Container for Record Engine
oops - apk..TBlankenheim wrote: ↑Mon Aug 10, 2020 1:46 pmIs this something I should be able to do in the current container? Doesn't look like apt is a supported command unless I'm missing something obvious.using 'apt add wget' installs a usable version
Am working on updating the container.. for some reason though the PUID/PGID mods are breaking.. going to back them out so we have working container at least
Re: unofficial Docker Container for Record Engine
Posted a new version on DockerHub
This just gets the beta update working.
Still working on the PUID/PGID..
Thought I had something working, but once I pop the script into the Alpine container it doesn't work.
Will continue working it.
This just gets the beta update working.
Still working on the PUID/PGID..
Thought I had something working, but once I pop the script into the Alpine container it doesn't work.
Will continue working it.
-
- Posts: 101
- Joined: Wed May 27, 2015 9:15 am
- Device ID: 107BBE13, 10782AED
- Location: Madison, WI
- x 2
Re: unofficial Docker Container for Record Engine
That did the trick. Thanks!Posted a new version on DockerHub
On unRAID, I can easily pass in the --user="<PUID>:<PGID>" parameter, so I have a workaround.Still working on the PUID/PGID..
Thought I had something working, but once I pop the script into the Alpine container it doesn't work.
Will continue working it.
Thanks again for all your work!
Re: unofficial Docker Container for Record Engine
If I'm running this on unRaid and I grabbed your docker via Community Apps / DockerHub will it recognize that you pushed an update? I know the dockers installed from Community Apps recognize an update but I'm not so sure if Community Apps+DockerHub works that way...
-
- Posts: 101
- Joined: Wed May 27, 2015 9:15 am
- Device ID: 107BBE13, 10782AED
- Location: Madison, WI
- x 2
Re: unofficial Docker Container for Record Engine
Probably a question better directed at the unRAID forums, but I believe that everything works the same. Seems to work for me at least.If I'm running this on unRaid and I grabbed your docker via Community Apps / DockerHub will it recognize that you pushed an update? I know the dockers installed from Community Apps recognize an update but I'm not so sure if Community Apps+DockerHub works that way...
Re: unofficial Docker Container for Record Engine
TBlankenheim wrote: ↑Tue Sep 08, 2020 10:30 amIs there some way to check which version is currently installed on my system then?Probably a question better directed at the unRAID forums, but I believe that everything works the same. Seems to work for me at least.
-
- Posts: 101
- Joined: Wed May 27, 2015 9:15 am
- Device ID: 107BBE13, 10782AED
- Location: Madison, WI
- x 2
Re: unofficial Docker Container for Record Engine
Not exactly sure how to check the version of the container, but you could always CHECK FOR UPDATES on the Docker tab and see if hdhrdvr-docker is up-to-date and update if necessary.Is there some way to check which version is currently installed on my system then?