This is a problem too -- on Synology. On that specific NAS, Docker can't create directories -- they need to already exist. I believe /volume1/docker/olivetin is a good option. Make sure (using File Station) those directories exist first. Create them if needed. This is required for all containers, and is a Synology-Docker issue.
EDIT: Also, create /volume1/docker/olivetin/data for static-file-server...
Understood. This update did the trick.
I tried the Tubi project. This installed. The MLB one click did not. The Roku Bridge Container is generated but I'll have to address this in the Custom channels in CDVR I think.
Glad to hear it.
Error messages?
The docker composes used for anything in Project One-Click are shown here, or can be displayed in One-Click:
This will help you figure out what directory to create before trying to spin-up a container. Only certain directories are writable on Synology. Using /volume1/docker as a parent (as opposed to /data) is a reasonably safe bet.
The Roku Bridge requires configuration before you can create your CDVR source. One-Click always does this if possible, but some projects need configuration before proceeding.
FOR MLB error:
JSON response from http://192.168.1.20:9000/api/stacks/create/standalone/string?endpointId=2:
{"message":"failed to deploy a stack: time=\"2026-01-19T20:30:09Z\" level=warning msg=\"/data/compose/24/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion\"\n Network mlbserver_default Creating\n Network mlbserver_default Created\n Container mlbserver Creating\n Container mlbserver Created\n Container mlbserver Starting\nError response from daemon: Bind mount failed: '/data/mlbserver' does not exists\n","details":"Failed to deploy a stack: time=\"2026-01-19T20:30:09Z\" level=warning msg=\"/data/compose/24/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion\"\n Network mlbserver_default Creating\n Network mlbserver_default Created\n Container mlbserver Creating\n Container mlbserver Created\n Container mlbserver Starting\nError response from daemon: Bind mount failed: '/data/mlbserver' does not exists\n"}
false
As discussed, you can't use /data as a parent on Synology. You should specify /volume1/docker as a parent, but be sure to create /volume1/docker/mlbserver using File Station first.
Ok, I got MLB to work. Samsung is working. The Weather4000 is up next but is asking for a cc4c Host. I don't know what this is but I'll have to research. Thanks so much for your help.
There are some projects that probably won't run well, if at all, on a low powered Synology NAS.
Those are meant for beefier machines.
I would recommend looking at the threads for the projects before you try installing them.
Good morning,
I spun up a Linux box just to run docker/portainer. I think I got close but seeing errors when I run HealthCheck. Any suggestions are appreciated. AI is running in circles.....
ls: /mnt/192.168.1.62-8089/.: Input/output error
ls: /mnt/192.168.1.62-8089_logs: Input/output error
ls: /mnt/192.168.1.62-8089_logs/.: Input/output error
Checking your OliveTin-for-Channels installation...
(extended_check=false)
OliveTin Container Version 2026.04.23
OliveTin Docker Compose Version 2025.08.25
----------------------------------------
Checking that your selected Channels DVR server (192.168.1.62: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
100 1276 100 1276 0 0 712k 0 --:--:-- --:--:-- --:--:-- 1246k
HTTP Status: 200
Effective URL: http://192.168.1.62:8089/
----------------------------------------
Checking that your selected Channels DVR server's data files (/mnt/192.168.1.62-8089) are accessible:
Folders with the names Database, Images, Imports, Logs, Movies, Streaming and TV should be visible...
total 8
drwxr-xr-x 2 1000 1000 4096 Mar 29 22:35 .
drwxr-xr-x 1 root root 4096 Apr 30 11:13 ..
drwxr-xr-x 2 1000 1000 0 Apr 30 08:31 Database
drwxr-xr-x 2 1000 1000 0 Apr 30 01:03 Images
drwxr-xr-x 2 1000 1000 0 Oct 14 2023 Imports
drwxr-xr-x 2 1000 1000 0 Apr 29 23:01 Logs
drwxr-xr-x 2 1000 1000 0 Apr 30 10:59 Metadata
drwxr-xr-x 2 1000 1000 0 Mar 29 22:35 Movies
drwxr-xr-x 2 1000 1000 0 Mar 29 22:35 Streaming
drwxr-xr-x 2 1000 1000 0 Apr 25 23:59 TV
Docker reports your current DVR_SHARE setting as...
/mnt/d/DVR
If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:
Channels reports this path as...
D:\DVR
When using WSL with a Linux distro and Docker Desktop, it's recommended to use...
/mnt/d/DVR
----------------------------------------
Checking that your selected Channels DVR server's log files (/mnt/192.168.1.62-8089_logs) are accessible:
Folders with the names data and latest should be visible...
total 8
drwxr-xr-x 2 1000 1000 4096 Mar 29 22:35 .
drwxr-xr-x 1 root root 4096 Apr 30 11:13 ..
drwxr-xr-x 2 1000 1000 0 Apr 30 08:31 Database
drwxr-xr-x 2 1000 1000 0 Apr 30 01:03 Images
drwxr-xr-x 2 1000 1000 0 Oct 14 2023 Imports
drwxr-xr-x 2 1000 1000 0 Apr 29 23:01 Logs
drwxr-xr-x 2 1000 1000 0 Apr 30 10:59 Metadata
drwxr-xr-x 2 1000 1000 0 Mar 29 22:35 Movies
drwxr-xr-x 2 1000 1000 0 Mar 29 22:35 Streaming
drwxr-xr-x 2 1000 1000 0 Apr 25 23:59 TV
Docker reports your current LOGS_SHARE setting as...
/mnt/d/DVR
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 WSL with a Linux distro and Docker Desktop, it's recommended 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
Portainer Environment ID for local is
Portainer https response on port 9443 reports version 2.39.1
Portainer Environment ID for local is 3
----------------------------------------
Here's a list of your current OliveTin-related settings:
HOSTNAME=olivetin
CHANNELS_DVR=192.168.1.62:8089
CHANNELS_DVR_ALTERNATES=
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.86
PORTAINER_PORT=9443
PORTAINER_ENV=2
----------------------------------------
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
options edns0 trust-ad ndots:0
# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [host(127.0.0.53)]
# 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:: ip6-localnet
ff00:: ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.26.0.2 olivetin
Could you post the complete set of OliveTin env vars you're using, from the OliveTin stack?
Also, can you give me a picture of what systems you're using for what at this point? Is your QNAP still in the mix? Are you using a Windows PC as well?
You have a great memory. Here's what I am using:
Thanks for the help. Linux newbie.
Here's the environment info:
TAG=latest
DOMAIN=
HOST_PORT=1337
CHANNELS_DVR_HOST=192.168.1.62
CHANNELS_DVR_PORT=8089
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=
ALERT_EMAIL_FROM=
ALERT_EMAIL_PASS=
ALERT_EMAIL_TO=
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=US/Eastern
HOST_DIR=/home/jim/docker/olivetin/data
DVR_SHARE=/mnt/d/DVR
LOGS_SHARE=/mnt/d/DVR
TUBEARCHIVIST_SHARE=/mnt/d/dvr
DVR2_SHARE=
LOGS2_SHARE=
TUBEARCHIVIST2_SHARE=
DVR3_SHARE=
LOGS3_SHARE=
TUBEARCHIVIST3_SHARE=
HOST_SFS_PORT=8080
FOLDER=/web
cat: /config/olivetin.token: No such file or directory=
PORTAINER_TOKEN=xxxxxxxxxxx
PORTAINER_HOST=192.168.1.86
PORTAINER_PORT=9443
PORTAINER_ENV=2
PERSISTENT_LOGS=false
OK, that's helpful. Though there are multiple ways to do this, here's my typical approach:
On your Windows system running CDVR, have the folder where you store DVR recordings and "Personal Media" set up as a Samba shares. Also, have the location where CDVR program files also set up as a Samba share.
Here's mine, where dvr is my CDVR recordings folder. TV Series and Movies are personal media folders, and ChannelsDVR is a Samba share of my CDVR programs (aka executables):
The dvr share contains these files:
And, the ChannelsDVR share contains:
Then, in Portainer, you need to create Docker Volumes to access those shares:
A volume called channels-dvr:
And a volume called channels-dvr-logs:
The above, I would consider the "easy way" to attach Samba shares to a Docker container. It's also possible to mount Samba shares to your file system, and then use those mount points, but that's a bit more complicated.
In your OliveTin stack, you'd then uncomment the lines that include #0#, #1#, and #2#, like this:
volumes: # Remove the #x# to enable. Use this section if you've setup a docker volume named channels-dvr, with CIFS or NFS, to bind to /mnt/dvr inside the container. Set ${DVR_SHARE} to channels-dvr (DVR_SHARE=channels_dvr) in that example.
channels-dvr:
external: true
channels-dvr-logs:
external: true
#3#tubearchivist:
#3#external: true
#4#channels-dvr2:
#4#external: true
#5#channels-dvr2-logs:
#5#external: true
#6#tubearchivist2:
#6#external: true
#7#channels-dvr3:
#7#external: true
#8#channels-dvr3-logs:
#8#external: true
#9#tubearchivist3:
#9#external: true
Finally, you'd modify these two env vars to use these new volume names rather than paths, like so:
DVR_SHARE=channels-dvr
LOGS_SHARE=channels-dvr-logs
Thanks. Got Samba shares done. Will attempt the rest tonight. Thanks for getting back so quickly.
I think you got me there. Now I will see about moving my docker into OliveTin. I am copying my healthcheck just to in case you see something I didn't address. Thanks again.
Checking your OliveTin-for-Channels installation...
(extended_check=false)
OliveTin Container Version 2026.04.23
OliveTin Docker Compose Version 2025.03.26
----------------------------------------
Checking that your selected Channels DVR server (192.168.1.62: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
100 1276 100 1276 0 0 842k 0 --:--:-- --:--:-- --:--:-- 1246k
HTTP Status: 200
Effective URL: http://192.168.1.62:8089/
----------------------------------------
Checking that your selected Channels DVR server's data files (/mnt/192.168.1.62-8089) are accessible:
Folders with the names Database, Images, Imports, Logs, Movies, Streaming and TV should be visible...
total 8
drwxr-xr-x 2 root root 4096 Mar 29 22:35 .
drwxr-xr-x 1 root root 4096 May 1 11:50 ..
drwxr-xr-x 2 root root 0 May 1 09:04 Database
drwxr-xr-x 2 root root 0 May 1 02:01 Images
drwxr-xr-x 2 root root 0 Oct 14 2023 Imports
drwxr-xr-x 2 root root 0 Apr 29 23:01 Logs
drwxr-xr-x 2 root root 0 May 1 10:59 Metadata
drwxr-xr-x 2 root root 0 Mar 29 22:35 Movies
drwxr-xr-x 2 root root 0 Mar 29 22:35 Streaming
drwxr-xr-x 2 root root 0 Apr 25 23:59 TV
Docker reports your current DVR_SHARE setting as...
/var/lib/docker/volumes/channels-dvr/_data
If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:
Channels reports this path as...
D:\DVR
When using WSL with a Linux distro and Docker Desktop, it's recommended to use...
/mnt/d/DVR
----------------------------------------
Checking that your selected Channels DVR server's log files (/mnt/192.168.1.62-8089_logs) are accessible:
Folders with the names data and latest should be visible...
total 12
drwxr-xr-x 2 root root 4096 Apr 29 08:00 .
drwxr-xr-x 1 root root 4096 May 1 11:50 ..
drwxr-xr-x 2 root root 0 Apr 12 08:00 2026.04.12.0247
drwxr-xr-x 2 root root 0 Apr 21 08:00 2026.04.21.0659
drwxr-xr-x 2 root root 0 Apr 22 08:00 2026.04.21.2033
drwxr-xr-x 2 root root 0 Apr 23 08:00 2026.04.23.0705
drwxr-xr-x 2 root root 0 Apr 25 08:00 2026.04.25.0633
drwxr-xr-x 2 root root 0 Apr 27 08:00 2026.04.26.0749
-rwxr-xr-x 1 root root 829 Apr 29 08:00 Channels DVR Server.lnk
drwxr-xr-x 2 root root 0 May 1 11:49 data
drwxr-xr-x 2 root root 0 Apr 29 08:00 latest
Docker reports your current LOGS_SHARE setting as...
/var/lib/docker/volumes/channels-dvr-logs/_data
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 WSL with a Linux distro and Docker Desktop, it's recommended 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
Portainer Environment ID for local is
Portainer https response on port 9443 reports version 2.21.4
Portainer Environment ID for local is
----------------------------------------
Here's a list of your current OliveTin-related settings:
HOSTNAME=olivetin
CHANNELS_DVR=192.168.1.62:8089
CHANNELS_DVR_ALTERNATES=another-server:8089 a-third-server:8089
CHANNELS_CLIENTS=appletv4k
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=[Redacted]@gmail.com
ALERT_EMAIL_PASS=[Redacted]
ALERT_EMAIL_TO=[Redacted]@att.net
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
PORTAINER_TOKEN=[Redacted]
PORTAINER_HOST=192.168.1.86
PORTAINER_PORT=9443
PORTAINER_ENV=2
----------------------------------------
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 localdomain
options edns0 trust-ad ndots:0
# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [host(127.0.0.53)]
# 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:: ip6-localnet
ff00:: ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.27.0.3 olivetin
It looks like you're only using https:// (port 9443) for Portainer, which is fine, but the fact that no Environment ID is reported likely means your Portainer token is no longer valid. Create a new one, and use it in your OliveTin stack. You won't be good-to-go until you see both a version number and ID on port 9000 or port 9443.
Remove the sample values from these two env vars.
Fix those things, and run the healthcheck again to confirm success.
Two issues. If I remove env for a third server, it breaks the container with trailing space error. When I put it back, all seem good. Also, I can't make OliveTin see the PORTAINER_TOKEN.
Checking your OliveTin-for-Channels installation...
(extended_check=false)
OliveTin Container Version 2026.04.23
OliveTin Docker Compose Version 2025.03.26
----------------------------------------
Checking that your selected Channels DVR server (192.168.1.62: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
100 1276 100 1276 0 0 466k 0 --:--:-- --:--:-- --:--:-- 623k
HTTP Status: 200
Effective URL: http://192.168.1.62:8089/
----------------------------------------
Checking that your selected Channels DVR server's data files (/mnt/192.168.1.62-8089) are accessible:
Folders with the names Database, Images, Imports, Logs, Movies, Streaming and TV should be visible...
total 8
drwxr-xr-x 2 root root 4096 Mar 29 22:35 .
drwxr-xr-x 1 root root 4096 May 1 15:50 ..
drwxr-xr-x 2 root root 0 May 1 09:04 Database
drwxr-xr-x 2 root root 0 May 1 13:01 Images
drwxr-xr-x 2 root root 0 Oct 14 2023 Imports
drwxr-xr-x 2 root root 0 Apr 29 23:01 Logs
drwxr-xr-x 2 root root 0 May 1 13:00 Metadata
drwxr-xr-x 2 root root 0 Mar 29 22:35 Movies
drwxr-xr-x 2 root root 0 Mar 29 22:35 Streaming
drwxr-xr-x 2 root root 0 Apr 25 23:59 TV
Docker reports your current DVR_SHARE setting as...
/var/lib/docker/volumes/channels-dvr/_data
If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:
Channels reports this path as...
D:\DVR
When using WSL with a Linux distro and Docker Desktop, it's recommended to use...
/mnt/d/DVR
----------------------------------------
Checking that your selected Channels DVR server's log files (/mnt/192.168.1.62-8089_logs) are accessible:
Folders with the names data and latest should be visible...
total 12
drwxr-xr-x 2 root root 4096 Apr 29 08:00 .
drwxr-xr-x 1 root root 4096 May 1 15:50 ..
drwxr-xr-x 2 root root 0 Apr 12 08:00 2026.04.12.0247
drwxr-xr-x 2 root root 0 Apr 21 08:00 2026.04.21.0659
drwxr-xr-x 2 root root 0 Apr 22 08:00 2026.04.21.2033
drwxr-xr-x 2 root root 0 Apr 23 08:00 2026.04.23.0705
drwxr-xr-x 2 root root 0 Apr 25 08:00 2026.04.25.0633
drwxr-xr-x 2 root root 0 Apr 27 08:00 2026.04.26.0749
-rwxr-xr-x 1 root root 829 Apr 29 08:00 Channels DVR Server.lnk
drwxr-xr-x 2 root root 0 May 1 15:24 data
drwxr-xr-x 2 root root 0 Apr 29 08:00 latest
Docker reports your current LOGS_SHARE setting as...
/var/lib/docker/volumes/channels-dvr-logs/_data
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 WSL with a Linux distro and Docker Desktop, it's recommended 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
Portainer Environment ID for local is
Portainer https response on port 9443 reports version 2.41.0
Portainer Environment ID for local is
----------------------------------------
Here's a list of your current OliveTin-related settings:
HOSTNAME=olivetin
CHANNELS_DVR=192.168.1.62:8089
CHANNELS_DVR_ALTERNATES=
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=[Redacted]@gmail.com
ALERT_EMAIL_PASS=[Redacted]
ALERT_EMAIL_TO=[Redacted]@att.net
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
PORTAINER_TOKEN=[Redacted]
PORTAINER_HOST=192.168.1.86
PORTAINER_PORT=9443
PORTAINER_ENV=2
----------------------------------------
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 localdomain
options edns0 trust-ad ndots:0
# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [host(127.0.0.53)]
# 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:: ip6-localnet
ff00:: ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.27.0.3 olivetin
You're not using the latest Docker Compose for OliveTin. When you're setting things up manually, like you're doing (not using EZ-Start), those can always be found here:
You had it working in your original post about this, I'm guessing maybe you started over, and are using an old token? Generate a new one, and copy-and-paste it into your stack.
EDIT: Also, just to confirm, you didn't mess with the default Portainer environment name of local did you?
I am still failing. I have moved everything to portainer successfully. I have verified with cli that Olivetin can see Portainer and the token is valid. But it doesn't seem to reach it in Olivetin.
Here is a fresh healthcheck:
Checking your OliveTin-for-Channels installation...
(extended_check=false)
OliveTin Container Version 2026.04.23
OliveTin Docker Compose Version 2025.03.26
----------------------------------------
Checking that your selected Channels DVR server (192.168.1.62: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
100 1276 100 1276 0 0 475k 0 --:--:-- --:--:-- --:--:-- 623k
HTTP Status: 200
Effective URL: http://192.168.1.62:8089/
----------------------------------------
Checking that your selected Channels DVR server's data files (/mnt/192.168.1.62-8089) are accessible:
Folders with the names Database, Images, Imports, Logs, Movies, Streaming and TV should be visible...
total 8
drwxr-xr-x 2 root root 4096 Mar 29 22:35 .
drwxr-xr-x 1 root root 4096 May 1 21:27 ..
drwxr-xr-x 2 root root 0 May 1 09:04 Database
drwxr-xr-x 2 root root 0 May 1 13:01 Images
drwxr-xr-x 2 root root 0 Oct 14 2023 Imports
drwxr-xr-x 2 root root 0 Apr 29 23:01 Logs
drwxr-xr-x 2 root root 0 May 1 13:00 Metadata
drwxr-xr-x 2 root root 0 Mar 29 22:35 Movies
drwxr-xr-x 2 root root 0 Mar 29 22:35 Streaming
drwxr-xr-x 2 root root 0 Apr 25 23:59 TV
Docker reports your current DVR_SHARE setting as...
/var/lib/docker/volumes/channels-dvr/_data
If the listed folders are NOT visible, AND you have your Channels DVR and Docker on the same system:
Channels reports this path as...
D:\DVR
When using WSL with a Linux distro and Docker Desktop, it's recommended to use...
/mnt/d/DVR
----------------------------------------
Checking that your selected Channels DVR server's log files (/mnt/192.168.1.62-8089_logs) are accessible:
Folders with the names data and latest should be visible...
total 12
drwxr-xr-x 2 root root 4096 Apr 29 08:00 .
drwxr-xr-x 1 root root 4096 May 1 21:27 ..
drwxr-xr-x 2 root root 0 Apr 12 08:00 2026.04.12.0247
drwxr-xr-x 2 root root 0 Apr 21 08:00 2026.04.21.0659
drwxr-xr-x 2 root root 0 Apr 22 08:00 2026.04.21.2033
drwxr-xr-x 2 root root 0 Apr 23 08:00 2026.04.23.0705
drwxr-xr-x 2 root root 0 Apr 25 08:00 2026.04.25.0633
drwxr-xr-x 2 root root 0 Apr 27 08:00 2026.04.26.0749
-rwxr-xr-x 1 root root 829 Apr 29 08:00 Channels DVR Server.lnk
drwxr-xr-x 2 root root 0 May 1 21:24 data
drwxr-xr-x 2 root root 0 Apr 29 08:00 latest
Docker reports your current LOGS_SHARE setting as...
/var/lib/docker/volumes/channels-dvr-logs/_data
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 WSL with a Linux distro and Docker Desktop, it's recommended 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
Portainer Environment ID for local is
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.1.62:8089
CHANNELS_DVR_ALTERNATES=
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=[Redacted]@gmail.com
ALERT_EMAIL_PASS=[Redacted]
ALERT_EMAIL_TO=[Redacted]@att.net
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
PORTAINER_TOKEN=[Redacted]
PORTAINER_HOST=docker-host
PORTAINER_PORT=9443
PORTAINER_ENV=1
----------------------------------------
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 localdomain
options edns0 trust-ad ndots:0
# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [host(127.0.0.53)]
# 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:: ip6-localnet
ff00:: ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.27.0.3 olivetin
You're moving in the wrong direction. In your first post in this series, you were reaching Portainer, and your token was working. The only issue was your DVR_SHARE and LOGS_SHARE setup:
In your next post you were reaching Portainer, but your token was no longer working:
And now, in your most recent post, you're no longer reaching Portainer at all. I'm guessing AI is leading you astray:
EDIT: I'm also noticing, in comparing the above, you've ended up on a outdated version of Portainer. That was between your first and second posted healthchecks.
EDIT2: Also, you still haven't updated your OliveTin Docker compose.