unofficial Docker Container for Record Engine
Re: unofficial Docker Container for Record Engine
How can I verify which version of the recording engine I am running? I am using Unraid. I understand with every docker image restart it is pulling down a new version if needed. Thanks
-
- Silicondust
- Posts: 64
- Joined: Thu Mar 02, 2023 10:48 am
- Device ID: 108042A1, 10814D8E
- Location: Portugal
- x 1
Re: unofficial Docker Container for Record Engine
You have multiple waysKingLear wrote: Tue Jan 28, 2025 1:49 am How can I verify which version of the recording engine I am running? I am using Unraid. I understand with every docker image restart it is pulling down a new version if needed. Thanks
1. The container contains a simple web based UI at the DVRUI_PORT you provided to the container and will show you the version in both the header, and the entry for the engine -> http://<ip address>:<DVRUI_PORT>
2. The DVR Record Engine also contains it's web based UI at the Port in it's configuration which by default with the container is set to 59090 -> http://<ip address>:59090
3. In the recording volume there are bunch of log files created by the DVR Record Engine - the first line of each should contain the DVR engine version, e.g.
Code: Select all
HDHomeRun RECORD 20250117beta1 Linux xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx
Re: unofficial Docker Container for Record Engine
@rikd
Thoughts on why your recording engine appears so much newer than mine? How does the engine get updates? I assume that's not part of the container image?
HDHomeRun RECORD 20231214 Linux D19DAB15-D68D-AE46-4E39-70382DB8C1E2
Thoughts on why your recording engine appears so much newer than mine? How does the engine get updates? I assume that's not part of the container image?
HDHomeRun RECORD 20231214 Linux D19DAB15-D68D-AE46-4E39-70382DB8C1E2
-
- Expert
- Posts: 11424
- Joined: Wed Jan 24, 2007 1:04 am
- Device ID: 10A05954 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
- x 39
Re: unofficial Docker Container for Record Engine
Most likely you haven't chosen to install betas as that is the release version.
Re: unofficial Docker Container for Record Engine
BetaEngine is set to 1 in the Record Engine Parameters And Controls
-
- Silicondust
- Posts: 64
- Joined: Thu Mar 02, 2023 10:48 am
- Device ID: 108042A1, 10814D8E
- Location: Portugal
- x 1
Re: unofficial Docker Container for Record Engine
it will update the engine on restart of the container.NewGuy wrote: Sun Feb 02, 2025 11:06 am BetaEngine is set to 1 in the Record Engine Parameters And Controls
it doesn't update automatically while running at this time.
Re: unofficial Docker Container for Record Engine
I restarted the container and that did update it. Thanks. I'm surprised the container hadn't restarted in so long, but maybe there just haven't been a lot of engine updates since the 20231214 release.
Re: unofficial Docker Container for Record Engine
I'm having trouble getting this working fully on a UGreen Nas. I have this image created and running on docker inside UGOS. The engine is running and I was able to record shows inside the HDHomeRun app. I can also confirm the shows are recorded in the shared folders. I can watch the recordings from the shared folders. However when I go to the HDHomeRun app, I dont see the recorded shows in the Recorded tab. Is that normal? If not, any idea how to fix it?
Thanks,
Kev.
************************************************
Starting DVR Container
VERSION: 0.2.4 [x86_64]
************************************************
INFO: DVR data folder exists already
INFO: DVR Data folder is linked
INFO: DVR Folder linked to correct folder /dvrdata
INFO: DVR recordings folder exists already
INFO: DVR recordings folder is linked
INFO: DVR recordings Folder linked to correct folder /dvrrec
INFO: PHP WWW Server config file is missing, pulling from defaults...
INFO: Attempting requested User mapping
INFO: From root:root to 1000:10
INFO: Creating Group dvr with GID [10]
INFO: Success
INFO: Creating User dvr with UID [1000]
INFO: Success
INFO: Updating Nginx User
INFO: user with UID [1000] exists, checking GID...
INFO: group with GID [10] exists, updating NGinx config
INFO: Updating PHP User
INFO: user with UID [1000] exists, updating php config
INFO: group with GID [10] exists, updating php config
INFO: Attempting to Fixing Permissions
INFO: Updating the NGINX Port for UI to 10080
2025-06-04 18:39:30,532 INFO Set uid to user 0 succeeded
2025-06-04 18:39:30,534 INFO supervisord started with pid 38
2025-06-04 18:39:31,539 INFO spawned: 'dvr' with pid 39
2025-06-04 18:39:31,541 INFO spawned: 'nginx' with pid 40
2025-06-04 18:39:31,543 INFO spawned: 'php-fpm' with pid 41
**********************
hdhomerun.sh
DVRMgr: ** Validating the Config File is available and set up correctly
DVRMgr: Config File exists and is writable - is record path and port correct
DVRMgr: ** Installing the HDHomeRunDVR Record Engine
[04-Jun-2025 18:39:31] NOTICE: fpm is running, pid 41
[04-Jun-2025 18:39:31] NOTICE: ready to handle connections
DVRMgr: ** Current Engine Version is 20250506
DVRMgr: Downloading latest Stable release
DVRMgr: Got Engine 20250506
DVRMgr: Downloading latest Beta release
DVRMgr: Got Engine 20250506 [0]
DVRMgr: Beta version downloaded - check if [20250506] newer than [20250506]
DVRMgr: Beta version is not newer than existing engine - not updating
DVRMgr: Engine Updated to... 20250506
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
DVRMgr: ** Executing DVR engine with PUID info...
2025-06-04 18:39:33,050 INFO success: dvr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-04 18:39:33,050 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-04 18:39:33,050 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Thanks,
Kev.
************************************************
Starting DVR Container
VERSION: 0.2.4 [x86_64]
************************************************
INFO: DVR data folder exists already
INFO: DVR Data folder is linked
INFO: DVR Folder linked to correct folder /dvrdata
INFO: DVR recordings folder exists already
INFO: DVR recordings folder is linked
INFO: DVR recordings Folder linked to correct folder /dvrrec
INFO: PHP WWW Server config file is missing, pulling from defaults...
INFO: Attempting requested User mapping
INFO: From root:root to 1000:10
INFO: Creating Group dvr with GID [10]
INFO: Success
INFO: Creating User dvr with UID [1000]
INFO: Success
INFO: Updating Nginx User
INFO: user with UID [1000] exists, checking GID...
INFO: group with GID [10] exists, updating NGinx config
INFO: Updating PHP User
INFO: user with UID [1000] exists, updating php config
INFO: group with GID [10] exists, updating php config
INFO: Attempting to Fixing Permissions
INFO: Updating the NGINX Port for UI to 10080
2025-06-04 18:39:30,532 INFO Set uid to user 0 succeeded
2025-06-04 18:39:30,534 INFO supervisord started with pid 38
2025-06-04 18:39:31,539 INFO spawned: 'dvr' with pid 39
2025-06-04 18:39:31,541 INFO spawned: 'nginx' with pid 40
2025-06-04 18:39:31,543 INFO spawned: 'php-fpm' with pid 41
**********************
hdhomerun.sh
DVRMgr: ** Validating the Config File is available and set up correctly
DVRMgr: Config File exists and is writable - is record path and port correct
DVRMgr: ** Installing the HDHomeRunDVR Record Engine
[04-Jun-2025 18:39:31] NOTICE: fpm is running, pid 41
[04-Jun-2025 18:39:31] NOTICE: ready to handle connections
DVRMgr: ** Current Engine Version is 20250506
DVRMgr: Downloading latest Stable release
DVRMgr: Got Engine 20250506
DVRMgr: Downloading latest Beta release
DVRMgr: Got Engine 20250506 [0]
DVRMgr: Beta version downloaded - check if [20250506] newer than [20250506]
DVRMgr: Beta version is not newer than existing engine - not updating
DVRMgr: Engine Updated to... 20250506
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
DVRMgr: ** Executing DVR engine with PUID info...
2025-06-04 18:39:33,050 INFO success: dvr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-04 18:39:33,050 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-04 18:39:33,050 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
-
- Silicondust
- Posts: 64
- Joined: Thu Mar 02, 2023 10:48 am
- Device ID: 108042A1, 10814D8E
- Location: Portugal
- x 1
Re: unofficial Docker Container for Record Engine
what's your docker command line?h61882 wrote: Wed Jun 04, 2025 11:51 am I'm having trouble getting this working fully on a UGreen Nas. I have this image created and running on docker inside UGOS. The engine is running and I was able to record shows inside the HDHomeRun app. I can also confirm the shows are recorded in the shared folders. I can watch the recordings from the shared folders. However when I go to the HDHomeRun app, I dont see the recorded shows in the Recorded tab. Is that normal? If not, any idea how to fix it?
startup log looks good, what is the engine log?
if the app isn't seeing the DVR is likely a networking issue. are you using host or bridge mode? is the NAS on the same subnet as the device running the app?
Re: unofficial Docker Container for Record Engine
I have been a long time HDHomeRun user and subscriber. Been running my install on a WD MyCloud Ultra Ext2 with no issues.
I recently have built a high end UnRaid server with 8 SATA drives. It 'occurred' to me as I started decommissioning my old NAS units, if my UnRaid could host (transfer from my MyCloud to the new UnRaid box) a HDHomeRun docker.
UnRaid apps do not contain a HDHomeRun docker, but then I found this thread and it seems to be viable.
The thread seems to suggest any updates to the HDHomeRun application will update if the docker is started and stopped.
I noticed the actual docker is several years old so is it still viable?
I recently have built a high end UnRaid server with 8 SATA drives. It 'occurred' to me as I started decommissioning my old NAS units, if my UnRaid could host (transfer from my MyCloud to the new UnRaid box) a HDHomeRun docker.
UnRaid apps do not contain a HDHomeRun docker, but then I found this thread and it seems to be viable.
The thread seems to suggest any updates to the HDHomeRun application will update if the docker is started and stopped.
I noticed the actual docker is several years old so is it still viable?