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
Former Member
4 years agoDocker (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...
Former Member
4 years agoThanks for all the extra info, that is really helpful!
What I think that happens, is that the data
volume (the second volume) has been created but is not accessible to the correct user. There are a few things we can try:
- You could try deleting the volume. If you can run docker-compose
commands, that can be done with docker-compose down -v
. Then try bringing it up again.
- Otherwise, you could also map the data volume to the same volume where the credentials are stored. For example:
```
version: "3.4"
services:
op-connect-api:
image: 1password/connect-api:latest
user: "1042"
ports:
- "8888:8080"
volumes:
- "./1password-credentials.json:/home/opuser/.op/1password-credentials.json"
- "./data:/home/opuser/.op/data"
op-connect-sync:
image: 1password/connect-sync:latest
user: "1042"
volumes:
- "./1password-credentials.json:/home/opuser/.op/1password-credentials.json"
- "./data:/home/opuser/.op/data"
volumes:
data:
```
Let me know if this changes anything.