Replies: 2 comments 2 replies
|
This seems to be working as expected judging from the docker compose docs: I think you want the long syntax, i.e.
In your example that would be: services:
app:
image: quay.io/pussthecatorg/breezewiki
labels:
- com.centurylinklabs.watchtower.enable=true
restart: unless-stopped
mon:
image: busybox
depends_on:
app:
restart: true
labels:
- com.centurylinklabs.watchtower.enable=true
restart: unless-stopped
stdin_open: true
tty: true
unmon:
image: busybox
depends_on:
app:
restart: true
restart: unless-stopped
stdin_open: true
tty: true |
2 replies
|
There was another ticket that gained more traction and led to a fix in version v1.20.2 Does that solve what you're experiencing as well? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, I am having issues with watchtower not respecting the dependency relationship set with the
depends_on:attribute.This is the compose of the stack I used for testing:
Watchtower is configured to run every day, but whenever I check with
docker compose ps, the "app" container has a lower uptime that the 2 dependents:I expected the "mon" and "unmon" containers to both be restarted whenever "app" is updated, so the uptime should be nearly identical.
The watchtower log has no mention at all of the dependent containers, just the one being updated. I also made sure not to enable rolling restarts.
Is this some misconfiguration on my side or an issue with how watchtower works?
This is my watchtower configuration for reference:
compose.yaml.envSome help would be greately appreciated.
All reactions