I've found a bit of a hiccup in the UID/GID implementation. Both of my NAS's (UNRAID & Synology) like to assign users a GID=100. Most shares on UNRAID have a UID=99 (nobody), and a GID=100 (users). If I try to use these values for the environment parameters (PUID=99, PGID=100), the docker will ...

For my Unraid 6.9.2 build I was able to get this installed at the terminal with the following format. docker run -d --name HDHomeRun-DVR \ --network host \ -e DVRUI_PORT=59080 \ -e PUID=1000 \ -e PGID=1000 \ -v /path/to/config:/dvrdata \ -v /path/to/recordings:/dvrrec \ demonrik/hdhrdvr-docker:late...

I've found a bit of a hiccup in the UID/GID implementation. Both of my NAS's (UNRAID & Synology) like to assign users a GID=100. Most shares on UNRAID have a UID=99 (nobody), and a GID=100 (users). If I try to use these values for the environment parameters (PUID=99, PGID=100), the docker will ...

Quick Note Going forward I've added a VERSION file This is read out during startup in the logs So to check which version - just check your container log for ************************************************ Starting DVR Container VERSION: 0.2.0 ************************************************ Where 0...

NEW VERSION whoop - PUID/PGID is working!! Latest build just pushed to dockerhub - some repos like Unraid may take a few hours to see the update. Important If no PUID/PGID is specified through environment variables then it will default to root for the dvr engine. I see 1 or 2 issues there, and am w...

I finally got around to bringing up this docker on my Synology NAS (DS918+) as a failover to my UNRAID server. I followed the procedure posted here: https://forum.silicondust.com/forum/viewtopic.php?p=384521#p384521 The record engine was not starting due to a permission problem. Ownership for hdhom...

That is a little over my head. I would recommend you install Portainer first. see https://docs.portainer.io/v/ce-2.9/start/install/server/docker/linux This will help remove some of the confusion for you. Once that is installed you need to consider a few things you need a folder to store config file...

Running/recording for an hour. Stopped container to look at permissions drwxrwxrwx+ 1 root root 0 Jul 14 17:32 dvr -rwxrwxrwx+ 1 dvr 400 127 Jul 14 18:59 dvr.conf -rwxr-xr-x 1 dvr 400 1983318 Mar 3 13:39 hdhomerun_record drwxrwxrwx+ 1 root root 52 Jul 14 17:32 http drwxrwxrwx+ 1 root root 54 Jul 14...

1) Got the permission denied error due to rec engine owned by root drwxrwxrwx+ 1 dvr 400 0 Jul 11 07:58 dvr -rwxrwxrwx+ 1 dvr 400 128 Jul 11 11:04 dvr.conf -rwxrwxrwx+ 1 root root 1112605 Jul 12 13:29 hdhomerun_record_beta -rwxrwxrwx+ 1 root root 1983318 Mar 3 13:39 hdhomerun_record_rel drwxrwxrwx+...

While testing the root problem by starting/stopping the container last night I did a chown -R in a very wrong place. Almost finished rebuilding the nas. Have to rebuild the image as I never figured out how to push it to the repository. Should go faster this time :D I feel for you - easily done You ...

created new container to fix networking: docker run -d --name dvr --restart=unless-stopped --network host -e DVRUI_PORT=8080 -v /volume1/HD/data:/dvrdata -v /volume1/HD/recordings:/dvrrec localdvr:latest 1) Got the permission denied error due to rec engine owned by root drwxrwxrwx+ 1 dvr 400 0 Jul ...

New builds posted to dockerhub.com
Now has builds for armv7, aarch64 (sometimes called arm64) and x86_64 (AMD64)
Should cover most supported NAS architectures.

Thx, that fixed the build. I can get the container running with no log errors if I chown dvr:dvr the record engine after a restart. Restarts set the engine back to root:root and random permissions, usually -x--------. Still befuddled by networking. I can get a system status page from mynasip:59090 ...

Thank you! Big learning curve...my most recent software course was in 1971, Fortran. This will be interesting. :) Update: Build failed at Step 6: Can't find php7 package. Step 6/36 : RUN apk add --no-cache php7...ERROR: unable to select packages: php7 (no such package)... The command '/bin/sh -c ap...

after deleting and restarting the container I got the same result. --x------ Could the dvr user be the problem? Originally I created a normal user account, with no password, then modified the /etc/passed file: dvr:x:1000:100:default user for HDHomerunDVR:/var/services/homes/dvr:/bin/false After cha...