unofficial Docker Container for Record Engine

Downloads & Instructions
Post Reply
demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

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

Code: Select all

************************************************

           Starting DVR Container
           VERSION: 0.2.0

************************************************
Where 0.2.0 is today's stable version.
If you don't have a VERSION code - you don't have the stable one from today - please update.

If your favorite GUI doesn't provide a means to read the logs..
you can SSH and execute the command

Code: Select all

docker logs <container name>

TBlankenheim
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

Post by TBlankenheim »

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 not come up. I've included the log file for your review.

Code: Select all

************************************************

           Starting DVR Container
           VERSION: 0.2.0

************************************************

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 99:100
ERROR: GID specified in PUID [100] already exists - please specify a valid GID - skipping
INFO: Creating User dvr with UID [99]
INFO: Success
INFO: Updating Nginx User
INFO: user with UID [99] exists, checking GID...
INFO: group with GID [100] exists, updating NGinx config
INFO: Updating PHP User
INFO: user with UID [99] exists, updating php config
INFO: group with GID [100] exists, updating php config
INFO: Attempting to Fixing Permissions
chown: unknown user/group dvr:dvr
chown: unknown user/group dvr:dvr
INFO: Updating the NGINX Port for UI to 80
2022-08-01 03:43:08,689 INFO Set uid to user 0 succeeded
2022-08-01 03:43:08,692 INFO supervisord started with pid 36
2022-08-01 03:43:09,694 INFO spawned: 'dvr' with pid 37
2022-08-01 03:43:09,695 INFO spawned: 'nginx' with pid 38
2022-08-01 03:43:09,696 INFO spawned: 'php-fpm' with pid 39
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
DVRMgr: Lets remove any existing engine - we're going to take the latest always....
DVRMgr: Checking it was deleted - if we can't remove it we can't update
DVRMgr: Downloading latest release
2022/08/01 03:43:09 [emerg] 38#38: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:09,705 INFO exited: nginx (exit status 1; not expected)
[01-Aug-2022 03:43:09] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:09] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:09] ERROR: FPM initialization failed
[01-Aug-2022 03:43:09] ERROR: FPM initialization failed
DVRMgr: Downloading latest beta
2022-08-01 03:43:10,473 INFO exited: php-fpm (exit status 78; not expected)
DVRMgr: Comparing which is newest
DVRMgr: Both versions are same - using the Release version
2022-08-01 03:43:11,082 INFO success: dvr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-08-01 03:43:11,083 INFO spawned: 'nginx' with pid 45
2022/08/01 03:43:11 [emerg] 45#45: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:11,087 INFO exited: nginx (exit status 1; not expected)
DVRMgr: Engine Updated to...  20220303
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
chown: unknown user/group dvr:dvr
DVRMgr: ** Executing DVR engine with PUID info...
ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied
2022-08-01 03:43:11,118 INFO exited: dvr (exit status 126; not expected)
2022-08-01 03:43:12,119 INFO spawned: 'dvr' with pid 60
2022-08-01 03:43:12,121 INFO spawned: 'php-fpm' with pid 61
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
DVRMgr: Lets remove any existing engine - we're going to take the latest always....
DVRMgr: Checking it was deleted - if we can't remove it we can't update
DVRMgr: Downloading latest release
[01-Aug-2022 03:43:12] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:12] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:12] ERROR: FPM initialization failed
[01-Aug-2022 03:43:12] ERROR: FPM initialization failed
DVRMgr: Downloading latest beta
2022-08-01 03:43:12,628 INFO exited: php-fpm (exit status 78; not expected)
DVRMgr: Comparing which is newest
DVRMgr: Both versions are same - using the Release version
2022-08-01 03:43:13,237 INFO success: dvr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-08-01 03:43:13,238 INFO spawned: 'nginx' with pid 67
2022/08/01 03:43:13 [emerg] 67#67: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:13,242 INFO exited: nginx (exit status 1; not expected)
DVRMgr: Engine Updated to...  20220303
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
chown: unknown user/group dvr:dvr
DVRMgr: ** Executing DVR engine with PUID info...
ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied
2022-08-01 03:43:13,269 INFO exited: dvr (exit status 126; not expected)
2022-08-01 03:43:14,271 INFO spawned: 'dvr' with pid 82
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
DVRMgr: Lets remove any existing engine - we're going to take the latest always....
DVRMgr: Checking it was deleted - if we can't remove it we can't update
DVRMgr: Downloading latest release
DVRMgr: Downloading latest beta
2022-08-01 03:43:14,680 INFO spawned: 'php-fpm' with pid 86
[01-Aug-2022 03:43:14] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:14] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:14] ERROR: FPM initialization failed
[01-Aug-2022 03:43:14] ERROR: FPM initialization failed
DVRMgr: Comparing which is newest
DVRMgr: Both versions are same - using the Release version
2022-08-01 03:43:15,101 INFO exited: php-fpm (exit status 78; not expected)
DVRMgr: Engine Updated to...  20220303
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
chown: unknown user/group dvr:dvr
DVRMgr: ** Executing DVR engine with PUID info...
ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied
2022-08-01 03:43:15,137 INFO exited: dvr (exit status 126; not expected)
2022-08-01 03:43:16,138 INFO gave up: dvr entered FATAL state, too many start retries too quickly
2022-08-01 03:43:17,139 INFO spawned: 'nginx' with pid 103
2022/08/01 03:43:17 [emerg] 103#103: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:17,143 INFO exited: nginx (exit status 1; not expected)
2022-08-01 03:43:18,144 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2022-08-01 03:43:18,145 INFO spawned: 'php-fpm' with pid 104
[01-Aug-2022 03:43:18] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:18] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:18] ERROR: FPM initialization failed
[01-Aug-2022 03:43:18] ERROR: FPM initialization failed
I'm thinking the implementation of linux used in the docker container already has a GID equal to 100, so attempting to create the dvr GID with a value of 100 errors out, and things go downhill from there. Easy enough to work around by using a value that doesn't conflict with the existing GIDs. I don't think UNRAID pays much attention to GID for the purpose of shares, so probably not a big deal for that implementation.

Not sure if you consider this a bug or a limitation, but thought I should make you aware of the issue.

Thanks!

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

TBlankenheim wrote: Sun Jul 31, 2022 9:47 pm 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 not come up. I've included the log file for your review.

Code: Select all

************************************************

           Starting DVR Container
           VERSION: 0.2.0

************************************************

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 99:100
ERROR: GID specified in PUID [100] already exists - please specify a valid GID - skipping
INFO: Creating User dvr with UID [99]
INFO: Success
INFO: Updating Nginx User
INFO: user with UID [99] exists, checking GID...
INFO: group with GID [100] exists, updating NGinx config
INFO: Updating PHP User
INFO: user with UID [99] exists, updating php config
INFO: group with GID [100] exists, updating php config
INFO: Attempting to Fixing Permissions
chown: unknown user/group dvr:dvr
chown: unknown user/group dvr:dvr
INFO: Updating the NGINX Port for UI to 80
2022-08-01 03:43:08,689 INFO Set uid to user 0 succeeded
2022-08-01 03:43:08,692 INFO supervisord started with pid 36
2022-08-01 03:43:09,694 INFO spawned: 'dvr' with pid 37
2022-08-01 03:43:09,695 INFO spawned: 'nginx' with pid 38
2022-08-01 03:43:09,696 INFO spawned: 'php-fpm' with pid 39
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
DVRMgr: Lets remove any existing engine - we're going to take the latest always....
DVRMgr: Checking it was deleted - if we can't remove it we can't update
DVRMgr: Downloading latest release
2022/08/01 03:43:09 [emerg] 38#38: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:09,705 INFO exited: nginx (exit status 1; not expected)
[01-Aug-2022 03:43:09] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:09] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:09] ERROR: FPM initialization failed
[01-Aug-2022 03:43:09] ERROR: FPM initialization failed
DVRMgr: Downloading latest beta
2022-08-01 03:43:10,473 INFO exited: php-fpm (exit status 78; not expected)
DVRMgr: Comparing which is newest
DVRMgr: Both versions are same - using the Release version
2022-08-01 03:43:11,082 INFO success: dvr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-08-01 03:43:11,083 INFO spawned: 'nginx' with pid 45
2022/08/01 03:43:11 [emerg] 45#45: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:11,087 INFO exited: nginx (exit status 1; not expected)
DVRMgr: Engine Updated to...  20220303
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
chown: unknown user/group dvr:dvr
DVRMgr: ** Executing DVR engine with PUID info...
ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied
2022-08-01 03:43:11,118 INFO exited: dvr (exit status 126; not expected)
2022-08-01 03:43:12,119 INFO spawned: 'dvr' with pid 60
2022-08-01 03:43:12,121 INFO spawned: 'php-fpm' with pid 61
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
DVRMgr: Lets remove any existing engine - we're going to take the latest always....
DVRMgr: Checking it was deleted - if we can't remove it we can't update
DVRMgr: Downloading latest release
[01-Aug-2022 03:43:12] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:12] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:12] ERROR: FPM initialization failed
[01-Aug-2022 03:43:12] ERROR: FPM initialization failed
DVRMgr: Downloading latest beta
2022-08-01 03:43:12,628 INFO exited: php-fpm (exit status 78; not expected)
DVRMgr: Comparing which is newest
DVRMgr: Both versions are same - using the Release version
2022-08-01 03:43:13,237 INFO success: dvr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-08-01 03:43:13,238 INFO spawned: 'nginx' with pid 67
2022/08/01 03:43:13 [emerg] 67#67: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:13,242 INFO exited: nginx (exit status 1; not expected)
DVRMgr: Engine Updated to...  20220303
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
chown: unknown user/group dvr:dvr
DVRMgr: ** Executing DVR engine with PUID info...
ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied
2022-08-01 03:43:13,269 INFO exited: dvr (exit status 126; not expected)
2022-08-01 03:43:14,271 INFO spawned: 'dvr' with pid 82
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
DVRMgr: Lets remove any existing engine - we're going to take the latest always....
DVRMgr: Checking it was deleted - if we can't remove it we can't update
DVRMgr: Downloading latest release
DVRMgr: Downloading latest beta
2022-08-01 03:43:14,680 INFO spawned: 'php-fpm' with pid 86
[01-Aug-2022 03:43:14] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:14] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:14] ERROR: FPM initialization failed
[01-Aug-2022 03:43:14] ERROR: FPM initialization failed
DVRMgr: Comparing which is newest
DVRMgr: Both versions are same - using the Release version
2022-08-01 03:43:15,101 INFO exited: php-fpm (exit status 78; not expected)
DVRMgr: Engine Updated to...  20220303
DVRMgr: ** Starting the DVR Engine
DVRMgr: ** Checking for PUID
DVRMgr: ** PUID user exists - adjusting permissions to dvrdata & dvrrec
chown: unknown user/group dvr:dvr
DVRMgr: ** Executing DVR engine with PUID info...
ash: /HDHomeRunDVR/data/hdhomerun_record: Permission denied
2022-08-01 03:43:15,137 INFO exited: dvr (exit status 126; not expected)
2022-08-01 03:43:16,138 INFO gave up: dvr entered FATAL state, too many start retries too quickly
2022-08-01 03:43:17,139 INFO spawned: 'nginx' with pid 103
2022/08/01 03:43:17 [emerg] 103#103: getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
nginx: [emerg] getgrnam("dvr") failed in /etc/nginx/nginx.conf:4
2022-08-01 03:43:17,143 INFO exited: nginx (exit status 1; not expected)
2022-08-01 03:43:18,144 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2022-08-01 03:43:18,145 INFO spawned: 'php-fpm' with pid 104
[01-Aug-2022 03:43:18] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:18] ERROR: [pool www] cannot get gid for group 'dvr'
[01-Aug-2022 03:43:18] ERROR: FPM initialization failed
[01-Aug-2022 03:43:18] ERROR: FPM initialization failed
I'm thinking the implementation of linux used in the docker container already has a GID equal to 100, so attempting to create the dvr GID with a value of 100 errors out, and things go downhill from there. Easy enough to work around by using a value that doesn't conflict with the existing GIDs. I don't think UNRAID pays much attention to GID for the purpose of shares, so probably not a big deal for that implementation.

Not sure if you consider this a bug or a limitation, but thought I should make you aware of the issue.

Thanks!
Working as expected when it encounters existing users/groups.
maybe something to see if I can clean those up in next update

Jsherman
Posts: 180
Joined: Mon Jul 20, 2015 1:59 am

Re: unofficial Docker Container for Record Engine

Post by Jsherman »

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:latest

I was also able to get to get the WebGUI on my Server at the port listed above.

One small issue is that the WebGui is not listed under the options of the DVR. Could this be added in future build?
https://imgur.com/a/aMnuIxS

Also one other suggestion. Perhaps for a future build, could you add the HDHR DVR Logo to the Docker Icon? Something like this?
Image

Thank you for all of your hard work on this!

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

Jsherman wrote: Sun Jul 31, 2022 10:44 pm 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:latest

I was also able to get to get the WebGUI on my Server at the port listed above.

One small issue is that the WebGui is not listed under the options of the DVR. Could this be added in future build?
https://imgur.com/a/aMnuIxS

Also one other suggestion. Perhaps for a future build, could you add the HDHR DVR Logo to the Docker Icon? Something like this?
Image

Thank you for all of your hard work on this!
The webgui and icon are not part of the container
is actually an Unraid template.
I fully intend to create an one, but was waiting until I had the PUID/PGID working as I wanted to do it just once.
fwiw.. you can add in yourself if you use the editor in Unraid and select advanced.

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

TBlankenheim wrote: Sun Jul 31, 2022 9:47 pm 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 not come up. I've included the log file for your review.

Code: Select all

<snip>
I'm thinking the implementation of linux used in the docker container already has a GID equal to 100, so attempting to create the dvr GID with a value of 100 errors out, and things go downhill from there. Easy enough to work around by using a value that doesn't conflict with the existing GIDs. I don't think UNRAID pays much attention to GID for the purpose of shares, so probably not a big deal for that implementation.

Not sure if you consider this a bug or a limitation, but thought I should make you aware of the issue.

Thanks!
Looked in to this and I believe I can do this pretty easily by adding the dvr user through useradd and not adduser.
This would allow me to reuse a UID/GID and would simplify the script quite a bit too
Is not a problem to have duplicate IDs - just needed a way to create them :)
I'll work on this for next release.

TBlankenheim
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

Post by TBlankenheim »

Looked in to this and I believe I can do this pretty easily by adding the dvr user through useradd and not adduser.
This would allow me to reuse a UID/GID and would simplify the script quite a bit too
Is not a problem to have duplicate IDs - just needed a way to create them :)
I'll work on this for next release.
Outstanding! :D

Thank you for all of your work!

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

NEW VERSION
Latest version pushed to DockerHub along with a tag for 0.2.1

This release will allow you to choose a PUID and PGID that already exist in the container, removing the constraint if the container has existing users or group IDs like 100, etc.
and thus you can ensure that the user matches an existing user on your NAS/Server.

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

Created a small guide for QNAP users to move from QPKG to Container
https://github.com/demonrik/HDHR-DVR-docker
I'll try and add the Portainer, Unraid and Asustor info up there soon.
Synology - sorry.. you're kinda on your own, but if someone wants to write one up and send to me, happy to publish and give credit.

TBlankenheim
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

Post by TBlankenheim »

demonrik wrote: Sat Aug 06, 2022 1:30 pm NEW VERSION
Latest version pushed to DockerHub along with a tag for 0.2.1

This release will allow you to choose a PUID and PGID that already exist in the container, removing the constraint if the container has existing users or group IDs like 100, etc.
and thus you can ensure that the user matches an existing user on your NAS/Server.
Works like a charm! 👍

Thank You!

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

NEW VERSION
Latest version pushed to DockerHub along with a tag for 0.2.2

This release fixes an issue when I removed the RunAs from the configuration files it prevented updating anything else in the configuration file.
Now fixed.

Jsherman
Posts: 180
Joined: Mon Jul 20, 2015 1:59 am

Re: unofficial Docker Container for Record Engine

Post by Jsherman »

demonrik wrote: Fri Aug 12, 2022 10:39 am NEW VERSION
Latest version pushed to DockerHub along with a tag for 0.2.2

This release fixes an issue when I removed the RunAs from the configuration files it prevented updating anything else in the configuration file.
Now fixed.
To get this to update on my Unraid build, I remove then reinstall it with the "docker run" command. It does not allow me to update in the docker tab by clicking on the icon. Could you suggest an easier alternative?

Thank you for your continued work on this!

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

Jsherman wrote: Sat Aug 13, 2022 8:36 am
demonrik wrote: Fri Aug 12, 2022 10:39 am NEW VERSION
Latest version pushed to DockerHub along with a tag for 0.2.2

This release fixes an issue when I removed the RunAs from the configuration files it prevented updating anything else in the configuration file.
Now fixed.
To get this to update on my Unraid build, I remove then reinstall it with the "docker run" command. It does not allow me to update in the docker tab by clicking on the icon. Could you suggest an easier alternative?

Thank you for your continued work on this!
It works for my Unraid server ?!?
I don't think I've done anything specific for it.
Make sure you are using 'latest' and not a specific version
Generally takes a day or so for the docker subsystem tab to identify that an update was pushed and it shows an update is available.
But usually you can hit the force update (maybe hidden under advanced view of docker) and it'll do it then.

Jsherman
Posts: 180
Joined: Mon Jul 20, 2015 1:59 am

Re: unofficial Docker Container for Record Engine

Post by Jsherman »

Thank you for your continued work on this!
[/quote]
It works for my Unraid server ?!?
I don't think I've done anything specific for it.
Make sure you are using 'latest' and not a specific version
Generally takes a day or so for the docker subsystem tab to identify that an update was pushed and it shows an update is available.
But usually you can hit the force update (maybe hidden under advanced view of docker) and it'll do it then.
[/quote]

Interesting. When I would update my other dockers in the past, it would say something along the lines of "this container cannot be updated from this source, did you install it from here". I am greatly paraphrasing mind you.

I was also getting "not available" in the update status before but now it shows up to date as shown here https://imgur.com/kzFoNH1

I will post more info when your next update is available.

demonrik
Posts: 1591
Joined: Mon May 04, 2015 10:03 am
Device ID: 108042A1, 10814D8E
x 38

Re: unofficial Docker Container for Record Engine

Post by demonrik »

Jsherman wrote: Sun Aug 14, 2022 9:30 am Thank you for your continued work on this!
It works for my Unraid server ?!?
I don't think I've done anything specific for it.
Make sure you are using 'latest' and not a specific version
Generally takes a day or so for the docker subsystem tab to identify that an update was pushed and it shows an update is available.
But usually you can hit the force update (maybe hidden under advanced view of docker) and it'll do it then.
Interesting. When I would update my other dockers in the past, it would say something along the lines of "this container cannot be updated from this source, did you install it from here". I am greatly paraphrasing mind you.

I was also getting "not available" in the update status before but now it shows up to date as shown here https://imgur.com/kzFoNH1

I will post more info when your next update is available.
If you edit the container - what is the entry you have for Repository?
If it's a tag with just one version - you will get that indicator because it can't find signatures to compare.
For example - if I use demonrik/hdhrdvr-docker:0.2.1 I will see what you see because there is no update to the 0.2.1 tag, just the one off build.
However, if I use (which I recommend) demonrik/hdhrdvr-docker:latest then it will have signatures to compare for old versions and sees you are up to date.

Post Reply