Triggering one manual backup, starts all backups #567
-
I have 3 docker-volume-backup containers running, each responsible for different volumes. When I try to run 1 manually to test, they all start. I'm assuming it's the result of the shared docker.sock, why is this necessary? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
This doesn't sound right somehow. Running docker exec like shown will not trigger processes in other containers, no matter the Docker socket. Are you sure this isn't an issue with your configuration and it does different things than you would expect it to? |
Beta Was this translation helpful? Give feedback.
-
@m90 I've found out more information. I've removed docker.sock from one of the containers and tried it then, and none are being triggered now. So I'm assuming that the shared docker socket triggers all containers instead of it being limited to the containers in the compose file. |
Beta Was this translation helpful? Give feedback.
This is expected, Docker does consider all containers on a host equal, no matter how you started them. You can use
BACKUP_EXEC_LABEL
to work around this and scope your commands to your compose stacks.