Project One-Click: All-in-One Installations of Docker Extensions and CDVR Custom Channels

chDVRuser · February 23, 2025, 2:46am

@bnhf
Here's my healthcheck from OT4C 2025-02-22

Checking your OliveTin-for-Channels installation...
(extended_check=false)

Version 2025.02.23

----------------------------------------

Checking that your selected Channels DVR server (192.168.1.4:8089) is reachable by URL:
HTTP Status: 200 indicates success...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1276  100  1276    0     0  16571      0 --:--:-- --:--:-- --:--:-- 16571
HTTP Status: 200
Effective URL: http://192.168.1.4:8089/

----------------------------------------

Checking that your selected Channels DVR server's data files (/mnt/192.168.1.4-8089) are accessible:
Folders with the names Database, Images, Imports, Logs, Movies, Streaming and TV should be visible...

total 72
drwxrwxrwx  2 1027 root    4096 Feb 10 15:22 #recycle
d--------- 11 1027 root    4096 Feb  9 12:52 .
drwxr-xr-x  4 root root    4096 Feb 22 18:39 ..
drwxrwxrwx  4 1027 root    4096 Feb  9 12:52 @eaDir
d--------- 32 1027 242120  4096 Feb 22 09:47 Database
d---------  3 1027 242120 20480 Feb 12 19:51 Images
d---------  5 1027 242120  4096 Mar 18  2022 Imports
d---------  4 1027 242120  4096 Feb 10  2022 Logs
d---------  2 1027 242120 12288 Jan  9 15:49 Movies
d---------  6 1027 242120  4096 Feb  9 20:27 Streaming
d--------- 55 1027 242120  4096 Feb 12 19:51 TV

If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:

Channels reports this path as...
/shares/dvr

----------------------------------------

Checking that your selected Channels DVR server's log files (/mnt/192.168.1.4-8089_logs) are accessible:
Folders with the names data and latest should be visible...

total 36
drwxr-xr-x  9 1027 users 4096 Feb 22 09:47 .
drwxr-xr-x  4 root root  4096 Feb 22 18:39 ..
drwxr-xr-x  2 root root  4096 Feb 16 20:08 2025.02.15.0247
drwxr-xr-x  2 root root  4096 Feb 17 18:00 2025.02.18.0129
drwxr-xr-x  2 root root  4096 Feb 18 14:51 2025.02.18.2211
drwxr-xr-x  2 root root  4096 Feb 19 10:22 2025.02.19.0538
drwxr-xr-x  2 root root  4096 Feb 19 12:23 2025.02.19.1823
drwxr-xr-x  2 root root  4096 Feb 22 09:47 2025.02.22.0936
drwxr-xr-x 13 root root  4096 Feb 22 18:15 data
lrwxrwxrwx  1 root root    15 Feb 22 09:47 latest -> 2025.02.22.0936

If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:

Channels reports this path as...
/channels-dvr

----------------------------------------

Checking if your Portainer token is working on ports 9000 and/or 9443:

Portainer http response on port 9000 reports version 2.27.0
Portainer Environment ID for local is 2
Portainer https response on port 9443 reports version 2.27.0
Portainer Environment ID for local is 2

----------------------------------------

Here's a list of your current OliveTin-related settings:

HOSTNAME=olivetin
CHANNELS_DVR=192.168.1.4:8089
CHANNELS_DVR_ALTERNATES=192.168.1.4:8189 192.168.1.4:8190 192.168.1.4:8289 192.168.1.4:8389 192.168.1.4:8489
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=
ALERT_EMAIL_FROM=[Redacted]@
ALERT_EMAIL_PASS=[Redacted]
ALERT_EMAIL_TO=[Redacted]@
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
PORTAINER_TOKEN=[Redacted]
PORTAINER_HOST=192.168.1.4
PORTAINER_PORT=9443
PORTAINER_ENV=

----------------------------------------

Here's the contents of /etc/resolv.conf from inside the container:

search local
nameserver 127.0.0.11
options ndots:0

----------------------------------------

Here's the contents of /etc/hosts from inside the container:

127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
172.19.0.2	olivetin

Not sure why it reports Version 2025.02.23

bnhf · February 23, 2025, 5:44am

My script that updates the date at build time must be using UTC. I'll see what I can do about it. Thanks for letting me know.

bnhf · February 23, 2025, 5:52am

To allow for leaving the TUBEARCHIVIST_SHARE value blank, go ahead and comment out this line in your Docker Compose. I'll make this the default as I update the OliveTin Compose on the forum tomorrow.

It'll look like this in the volumes: section from here forward:

      #- ${TUBEARCHIVIST_SHARE}:/mnt/${CHANNELS_DVR_HOST}-${CHANNELS_DVR_PORT}_ta # This can either be a Docker volume or a host directory that's connected via Samba or NFS to your TubeArchivist videos network share.

There's not a huge group of people using this Action, so it makes sense.

Channels2021 · February 23, 2025, 7:00am

Checking your OliveTin-for-Channels installation...
(extended_check=false)

Version 2025.02.22

----------------------------------------

Checking that your selected Channels DVR server (192.168.29.131:8089) is reachable by URL:
HTTP Status: 200 indicates success...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1276  100  1276    0     0   155k      0 --:--:-- --:--:-- --:--:--  178k
HTTP Status: 200
Effective URL: http://192.168.29.131:8089/

----------------------------------------

Checking that your selected Channels DVR server's data files (/mnt/192.168.29.131-8089) are accessible:
Folders with the names Database, Images, Imports, Logs, Movies, Streaming and TV should be visible...

total 4
drwxrwxrwx 1 root root  512 Feb 22 19:43 .
drwxr-xr-x 1 root root 4096 Feb 23 01:57 ..
drwxrwxrwx 1 root root  512 Feb 22 18:59 Database
drwxrwxrwx 1 root root  512 Feb 21 16:49 Images
drwxrwxrwx 1 root root  512 Feb 21 16:49 Imports
drwxrwxrwx 1 root root  512 Feb 21 17:46 Streaming
drwxrwxrwx 1 root root  512 Feb 22 19:44 olivetin

If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:

Channels reports this path as...
C:\ProgramData2\DVR

When using a Windows path in Portainer, change the backslashes to slashes like this...
C:/ProgramData2/DVR

When using WSL with a Linux distro and Docker Desktop, it's also possible to use...
/mnt/c/ProgramData2/DVR

----------------------------------------

Checking that your selected Channels DVR server's log files (/mnt/192.168.29.131-8089_logs) are accessible:
Folders with the names data and latest should be visible...

total 8
drwxrwxrwx 1 root root  512 Feb 21 16:54 .
drwxr-xr-x 1 root root 4096 Feb 23 01:57 ..
-rwxrwxrwx 1 root root  838 Feb 21 16:54 Channels DVR Server.lnk
drwxrwxrwx 1 root root  512 Feb 21 17:29 data
drwxrwxrwx 1 root root  512 Feb 21 16:54 latest

If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:

Channels reports this path as...
C:\ProgramData\ChannelsDVR

When using a Windows path in Portainer, change the backslashes to slashes like this...
C:/ProgramData/ChannelsDVR

When using WSL with a Linux distro and Docker Desktop, it's also possible to use...
/mnt/c/ProgramData/ChannelsDVR

----------------------------------------

Checking if your Portainer token is working on ports 9000 and/or 9443:

Portainer http response on port 9000 reports version 2.27.0
Portainer https response on port 9443 reports version 
Portainer Environment ID for local is 

----------------------------------------

Here's a list of your current OliveTin-related settings:

HOSTNAME=olivetin
CHANNELS_DVR=192.168.29.131:8089
CHANNELS_DVR_ALTERNATES=
CHANNELS_CLIENTS=192.168.29.245
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=[Redacted]@gmail.com
ALERT_EMAIL_PASS=[Redacted]
ALERT_EMAIL_TO=[Redacted]@gmail.com
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
PORTAINER_TOKEN=[Redacted]
PORTAINER_HOST=192.168.29.131
PORTAINER_PORT=
PORTAINER_ENV=

----------------------------------------

Here's the contents of /etc/resolv.conf from inside the container:

# Generated by Docker Engine.
# This file can be edited; Docker Engine will not make further changes once it
# has been modified.

nameserver 127.0.0.11
search local
options ndots:0

# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [192.168.65.7]
# Overrides: [search]
# Option ndots from: internal

----------------------------------------

Here's the contents of /etc/hosts from inside the container:

127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
172.19.0.2	olivetin

Channels2021 · February 23, 2025, 7:01am

TAG=latest
DOMAIN=local
HOST_PORT=1337
CHANNELS_DVR_HOST=192.168.29.131
CHANNELS_DVR_PORT=8089
CHANNELS_DVR2_HOST=
CHANNELS_DVR2_PORT=
CHANNELS_CLIENTS=192.168.29.245
ALERT_SMTP_SERVER=smtp.gmail.com:587
[email protected]
ALERT_EMAIL_PASS=xxxxxxxxxxxxxxxx
[email protected]
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=US/Eastern
HOST_DIR=C:/ProgramData
DVR_SHARE=C:/ProgramData2/DVR
LOGS_SHARE=C:/ProgramData/ChannelsDVR
TUBEARCHIVIST_SHARE=
HOST_SFS_PORT=8080
FOLDER=/web
PORTAINER_TOKEN=ptr_RoCJi+tUL6FZFHvZysHNd849xqbcREDDuQlKbqg8sl4=
PORTAINER_HOST=192.168.29.131
PORTAINER_PORT=9443

bnhf · February 23, 2025, 4:53pm

You didn't get most recent version of OliveTin before running this Action. It should have been 2025.02.23 (UTC time). Could you use the Re-pull and redeploy option, and run it again please?

Also, when you post logs, code snippets, yaml, env var lists and such on this forum -- be sure to use 3 backticks before and after the text, so that it ends up in an easier to read code block.

bnhf · February 23, 2025, 10:14pm

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.02.23) pushed late yesterday with support for DELETING Channels DVR Custom Channels sources, and associated Portainer stacks, created by Project One-Click. This makes it very easy to add an extension to check it out, and then remove it just as quickly and easily:

Screenshot 2025-02-23 140158

arizonaralph · February 24, 2025, 12:22am

THANK YOU FOR YOUR HELP!!! You and @chDVRuser ROCK!!!

chDVRuser · February 24, 2025, 2:36am

Confused

Looks like it was just pushed a couple hours ago https://hub.docker.com/r/bnhf/olivetin/tags.

bnhf · February 24, 2025, 2:59am

You miss little. I pushed an update shortly after the post as I realized it needed a tweak.

chDVRuser · February 24, 2025, 3:47am

Actually it's my DIUN that notified me.
I have it set to check all my images and also added some I'm not running to check on.

bnhf · February 25, 2025, 12:15am

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.02.24) pushed today, with an improvement to the new Delete a Project One-Click Channels DVR Extension Action.

For supported projects, this Action now:

Deletes any CDVR Custom Channels sources created for a given extension
Stops any running stacks created for a given extension
Deletes the stopped stack for a given extension
Deletes the container image pulled for a given extension (New!)

The last item, concerning deleting the image, is today's improvement. By deleting the image, this ensures that if a given extension is spun-up a later time, it will pull the latest as opposed to using the image present locally -- which could be out-of-date.

bnhf · February 25, 2025, 3:55am

@Channels2021 Have you had a chance to pull the :latest (now :2025.02.24) and re-run the healthcheck? If so, could you post it please?

Channels2021 · February 25, 2025, 5:04am

I removed that line and it loaded the stack before. The newest changes give me this error and the stack no longer loads. I am using the one from post #1 in this thread.

Failed to deploy a stack: failed to load the compose file: invalid spec: :/mnt/192.168.29.131-8089_ta: empty section between colons

bnhf · February 25, 2025, 4:53pm

That error can only be from that line I wanted you to comment out -- so something wasn't right the second time you did it. I've updated the compose in Post #1 now, so you can copy and paste it as is. Be sure to use the Re-pull and redeploy slider when you update the stack.

Channels2021 · February 28, 2025, 6:56am

I haven't been able to retest this but I will soon. Thanks a lot!

florlynch · March 3, 2025, 7:39pm

Hoping for some guidance. I've been using CDVR for a number of years, works well & have setup some docker containers for Frndly, Tubi & Tubo in addition to Xfinity TVE & HDHR antenna. I am running on an older Intel Mac mini that I would like to retire. I have recently installed OliveTin and moving the add-ins there. I wanted to move CDVR to my wife's very lightly used M4 Mac mini as she only does light web/email sporadically. Is there a recommended, secure way to setup on her Mac? I am currently the named Apple user on the Intel & I was planning on setting up myself as a named user on her Mini to migrate that over. However as I think of a fresh setup should I setup a more generic OS user on this Mac and only use for CDVR? I am Apple using screen sharing very successfully in the house (and Tailscale remotely). Appreciate any input, thanks in advance.

bnhf · March 3, 2025, 10:49pm

Makes sense to me to setup a separate user for CDVR and Docker/Portainer, but I'm not an everyday Mac user. Maybe @Fofer has some thoughts on this?

Fofer · March 3, 2025, 10:50pm

I have Channels DVR installed and running on my primary macOS user account. AFAIK this is the wisest path because otherwise it wouldn’t launch on its own after a reboot? As it stands now, as I understand it, I have to log in to the primary account first for CDVR hardware transcoding to work too. Maybe that’s outdated information now? I’m not really sure. Here's information I previously read that led me to those conclusions though:

jsfullam · March 6, 2025, 10:58pm

@bnhf, Unfortunately, I'm still having some trouble with the Project One-Click Plex TV action on my Synology Channels DVR server. It's getting the container up and running, and installing the Plex TV-NoEPG source without any problem. However, the Plex TV "gracenote=include" source isn't making it into Channels. Deleting the containers and sources using the one-click action is nice, so that I can repeat the installation easily as I am testing things.

JSON response from http://192.168.1.100:9000/api/stacks/create/standalone/string?endpointId=2:
{"Id":139,"Name":"plex-for-channels","Type":2,"EndpointId":2,"SwarmId":"","EntryPoint":"docker-compose.yml","Env":[{"name":"TAG","value":"latest"},{"name":"HOST_PORT","value":"7779"},{"name":"PORT","value":"7777"},{"name":"HOST_DIR","value":"/volume1/docker"}],"ResourceControl":{"Id":62,"ResourceId":"2_plex-for-channels","SubResourceIds":[],"Type":6,"UserAccesses":[],"TeamAccesses":[],"Public":false,"AdministratorsOnly":true,"System":false},"Status":1,"ProjectPath":"/data/compose/139","CreationDate":1741298723,"CreatedBy":"john","UpdateDate":0,"UpdatedBy":"","AdditionalFiles":null,"AutoUpdate":null,"Option":null,"GitConfig":null,"FromAppTemplate":false,"Namespace":""}
true
{"error":"invalid source url: Get \"http://192.168.1.100:7779/plex/playlist.m3u?regions=local\u0026gracenote=include\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
true