Closed bamartinez2 closed 1 year ago
Looks like the error is:
mkdir /data/G4 Doorbell: permission denied
which means that rclone does not have permissions to write to /data
, as per your compose file that looks like its /volume1/Protect Backups
on your host machine. Can you make sure that this directory is R/W for all users?
That was it - I expanded permissions on /volume1/Protect Backups to allow 'Everyone' R/W permissions. I was trying to have the container run as a specific user but was receiving an error that the account was not found in the passwd file... but it was in there. Which is why you see user: root in the docker-compose file. Super strange.
This will work for now I will work on limiting access at a later date perhaps! Thanks much!
Narrowed down to be a permissions issue with the shared folder in my NAS. Expanded to Everyone and alls working now.
This is a common issue with containers. It is caused by the user/group IDs not being consistent between the host OS and the container.
Please see here for details on fixing this: https://docs.linuxserver.io/general/understanding-puid-and-pgid
Description
Attempting to spin up unifi-protect-backup on my Synology NAS via portainer into docker. I am trying to read Protect recordings from my UDM SE, and store them locally on my NAS in its own Shared Folder.
What I Did
Attempted different iterations of a docker-compose stack deployment via portainer. The logs attached and docker-compose config shown is as close as I can get to working - but keep getting this permission denied error against what I think is activities looking for rclone. I installed rclone onto my NAS.. still getting the same errors. Looking for some advice/assistance with this one.