Just a thought, maybe add support for generating a adbtuner/apituner json for fios tv+ seeing as how verizon won't give out cablecards anymore.
Still getting the same error. I think I have the mnts to Channels ok but the host directory is killing me.
In Docker Desktop settings, you can find the paths that are allowed, but I know the /Users is one of them. Keep in mind upper/lowercase matters. You can open a terminal on the Mac, and do an ls -la /Users to see the subdirectories. One of them will be your Mac username:
slayer@Mac-Mini-M4 ~ % ls -la /Users
total 0
drwxr-xr-x 5 root admin 160 Aug 31 05:35 .
drwxr-xr-x 22 root wheel 704 Aug 12 20:51 ..
-rw-r--r-- 1 root wheel 0 Aug 12 20:51 .localized
drwxrwxrwt 13 root wheel 416 Aug 31 05:35 Shared
drwxr-x---+ 33 slayer staff 1056 Sep 4 19:50 slayer
So, in my case my HOST_DIR value would be /Users/slayer
We have made some headway as I think were getting past the local host directory.
This is the current error:
failed to deploy a stack: compose up operation failed: Error response from daemon: mounts denied: The path /mnt/channel-dvr is not shared from the host and is not known to Docker. You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing. See Change your Docker Desktop settings | Docker Docs for more info.
TAG=latest
DOMAIN=local
HOST_PORT=1337
CHANNELS_DVR_HOST=10.0.1.65
CHANNELS_DVR_PORT=8089
CHANNELS_DVR2_HOST=
CHANNELS_DVR2_PORT=
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=
ALERT_EMAIL_FROM=
ALERT_EMAIL_PASS=
ALERT_EMAIL_TO=
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=America/Chicago
HOST_DIR=/Users/alang
DVR_SHARE=/mnt/channel-dvr
LOGS_SHARE=/mnt/channel-dvr
TUBEARCHIVIST_SHARE=/mnt/channel-dvr
DVR2_SHARE=
LOGS2_SHARE=
TUBEARCHIVIST2_SHARE=
DVR3_SHARE=
LOGS3_SHARE=
TUBEARCHIVIST3_SHARE=
HOST_SFS_PORT=8080
FOLDER=/web
PORTAINER_TOKEN=(REDACTED)
PORTAINER_HOST=10.0.1.40
PORTAINER_PORT=9443
PORTAINER_ENV=2
PERSISTENT_LOGS=false
I got to call it a night. I will probably be out of touch to Sunday — Geaux Tigers
Docker Volumes are referenced by their name only. So, if you created one volume named channels-dvr, then that's the value you use for DVR_SHARE. Then, hopefully you created another Docker Volume called channels-dvr-logs, and that's the value you'd use for LOGS_SHARE. TUBEARCHIVIST_SHARE is usually the same value as DVR_SHARE.
You also need to un-comment a few things in the "volumes:" section. They start with #0#, #1# and #2#. That will define avolumes: section along with channels-dvr and channels-dvr-logs volumes specifically.
By uncommit, you mean just delete the #0#, etc.
I tried various things. One of the errors said can’t have more than one volumes. After a failed deploy, the items show back up commented out. Others say it can’t reach the Synology mints.
I’m pretty sure we have the host directory correct because it has created an olivetin folder ( nothing in it).
I'll redo the Volumes again tomorrow and post each step. The Mac has no issue navigating the Synology thru finder.
I'll sleep on it and try again tomorrow am.
Making some progress but not ready for prime time yet.
Using Host Directory as Users/alang and letting it think my DVR is on Mac allows it to spin up without errors. No need to run post health check yet.
Adding my Synology in still gives errors but I started using 'Gordon' in docker desktop to troubleshoot the errors. It actually created a volume named ChannelsDVR that connects with Synology and would spin up but it had an 8080 port conflict and switched to 8081. I'll redo later and stop that item running 8080 when I troubleshoot. Then everything should be good. In hindsight, I should have stopped that other piece in OliveTin the first time.
I'll have to add the channels log volume and let 'Gordon' do its work on that. I'll change the uncommented pieces to the actual volume Gordon creates.
Hopefully my next post will be the post install health check. Maybe tonight but probably tomorrow. Times are busy!!
1 Like