Pull from docker hub here https://hub.docker.com/r/demonrik/hdhrdvr-docker
Source is https://www.github.com/demonrik/HDHR-DVR-docker
Guides available for Qnap and Synology
Example docker run command
Code: Select all
docker run -d --name dvr \
--restart=unless-stopped \
--network host \
-v /path/to/hdhomerun/tempdata:/dvrdata \
-v /path/to/hdhomerun/recordings:/dvrrec \
-e DVRUI_PORT=10080 \
-e PUID=1000 \
-e PGID=1000 \
demonrik/hdhrdvr-docker
Synology NAS has no docker support for ARM based NAS, so haven't been able to test there as my Synology is ARM based
![Sad :(](./images/smilies/icon_e_sad.gif)
There are 3 environment variable/parameters to set/use.
DVRUI_PORT is the port for the DVR Manager php server - similar to the one installed in the SPK/APKG/QPKG. This will default to 80 if not set to something else which can conflict with other services, so highly recommended to set to something else like 59080
PUID and PGID allow you to map the DVR user within the container to a user on your NAS to ensure permissions matching. If not set the container will run everything as 'root' user. So recommend creating a DVR user, discover it's UID and GID and set these appropriately.
You will need 2 volumes you need to create or bind (recommended)
- /dvrrec recordings location
- /dvrdata Location to store the engine, config file and log of the script in the container
As you can see I use
Code: Select all
--network host
This is very important for HDHomeRun system to ensure everything is on the same network.
If you run the container and it's log is showing it's not seeing devices - chances are you missed this.
Once the container is running you can changes the dvr.conf file in your dvrdata to adjust the RecordStreamsMax..
Don't change the RecordPath
Also would recommend to NOT change the Port unless you know what you're doing.
Important that the engine has opportunity to write to the dvr.conf at least for the first time so it updates the StorageID.. Once done, you can make the dvr.conf read only.