Mine had been running 20220303, after restart now showing 20220822

Webstation is not required for the Docker version. For the .spk Webstation assures that you have PHP and a webserver. Since both are built into the docker container Webstation is not needed. If Webstaion is installed, it will not interfere. Use -e DVRUI_PORT=59080

You may not need to, the build script creates the dvr user and group and then sets the permissions. So after creating your mount point folders modify the docker run with the new paths, and run it again. The script contains: # Create default user and group & patch up permissions RUN addgroup -g 1...

Yes, running well. Thanks so much for your help. Next steps include: how to force a record engine to be primary when it has less free disk space. Quotas on dvr user had no effect. Setting the recordstreams=0 causes the engine to report freespace=Full. Not my kind of logic :lol: Assume that at some p...

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 ...

Here's the initial log, created when I first ran my Docker run command date stream content 2022-07-14T22:32:56.034008765Z stdout ************************************************ 2022-07-14T22:32:56.034116463Z stdout 2022-07-14T22:32:56.034172332Z stdout            Starting DVR Container 2022-07-14T2...

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 Success! 21 hours from a trashed N...

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 1...

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 b...

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 apk...

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 chan...

Stuck with this error: DVRMgr: ** Starting the DVR Engine as user dvr ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied 2022-06-23 15:01:10,003 INFO exited: dvr (exit status 126; not expected) Gotta be a permissions problem, but I'm not understanding where. -rwxrwxrwx+ 1 dvr 1000 80 Jun 18...

Created dvr user, edited /etc passwd, gave dvr user rw to both Docker and /volume1/HDHomerunDVR/dvrdata & /dvrrec . Attempting to map ports got "Port settings are not required when using the same network as Docker host" Maybe the problem is in my run command: docker run -d --name dvr \...

Progress: Installed Docker on Synology, container running, and see the record engine in /dvrdata. Nothing else happening. Logs show the dvr engine attempts to start as user dvr, permission denied. Yep, dvr user doesn't exist. Also: nginx: [emerg] 17272#17272: bind() to 0.0.0.0:80 failed (98: Address...

Thanks so much for your help. Success was easy when I just "cleaned house".