Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Docker (compose) Permission denied
I'm having trouble getting Connect up and running with Docker Compose. I believe my problems is somewhere related to a user and/or its rights. I am running Docker on my Synology NAS where I created a...
The folders are very specifically created by user opuser. No matter how I mount my volumes (- "data:..." or - "./data:...") I will keep having mismatched between the docker user and the host/folder. Do you agree with my findings? If so, what could we do to work around it :)
I think you're right here. Though that also suggests an alternative solution: what if you replace both volume mounts with this one: ./:/home/opuser/.op (make sure the 1password-credentials.json file is in ./). With a bit of luck, that works because the /home/opuser/.op is then owned by user 1042.
Alternatively, it is possible to execute a command during startup by modifying the entrypoint of one of the containers:
entrypoint: ["/bin/sh", "-c", "echo 'This text gets printed during startup' && connect-api"]
or
entrypoint: ["/bin/sh", "-c", "echo 'This text gets printed during startup' && connect-sync"]
One final thing worth checking: is it possible to choose which ID gets assigned to the user you create in the Synology software? If so, could you create one with ID 999?
