Hey,
This is exactly the functionality I was thinking about… really looking forward for this to be implemented.
Thanks for all your work and getting back to me.
Just released as (7.2.0)
This is amazing… thank you very much.
What’s the default trigger behaviour though? I’m guessing once it’s configured it applies to all containers without explicitly configured wud.trigger.exclude label?
… or is there another ENV var *_TRIGGERBYDEFAULT
Sorry I’ve not had a chance to look at the PR to see exactly what’s changed. I will take have look when I get back home.
Thanks for the update and your work
What’s the default trigger behaviour though? I’m guessing once it’s configured it applies to all containers without explicitly configured
wud.trigger.excludelabel?
Yes, you’re right.
By default, (when no wud.trigger.include neither wud.trigger.exclude are defined on a container), all triggers applies to the container.
I did a bit of testing now and something doesn’t work the way how it should… I think…
At high level, I have -
- approx 53 containers running across 4 Docker hosts
- the following two triggers configured
- WUD_TRIGGER_DOCKER_AUTOUPDATE_PRUNE=true
- WUD_TRIGGER_SMTP_XXX_HOST=xxx
- WUD_TRIGGER_SMTP_XXX_PORT=587
- WUD_TRIGGER_SMTP_XXX_FROM=wud@xxx
- WUD_TRIGGER_SMTP_XXX_TO=xxx@xxx
- 95% of all containers are configured with the following labels
- wud.watch
- wud.tag.include
- the remaining 5% of my containers now have the following labels
- wud.watch=false
- wud.trigger.exclude=WUD_TRIGGER_DOCKER_AUTOUPDATE_PRUNE
WUD_TRIGGER_DOCKER_AUTOUPDATE_PRUNE was disabled in my config before, so I was just getting SMTP notifications. I now installed version 7.2.0, enabled
WUD_TRIGGER_DOCKER_AUTOUPDATE_PRUNE trigger and added wud.trigger.exclude label to all containers I don’t want to automatically update.
It looks like WUD updated 2 containers on one of the hosts and then gave up with the rest for some reason… no errors, no nothing.
11:46:39.612 INFO whats-up-docker/watcher.docker.host1: Cron finished (4 containers watched, 0 errors, 0 available updates)
11:46:39.905 INFO whats-up-docker/watcher.docker.host2: Cron finished (3 containers watched, 0 errors, 0 available updates)
11:46:57.692 INFO whats-up-docker/watcher.docker.host2: Cron finished (22 containers watched, 0 errors, 7 available updates)
11:47:19.323 INFO whats-up-docker/watcher.docker.host4: Cron finished (24 containers watched, 0 errors, 8 available updates)
Hi, exclusions don’t apply to individual trigger properties.
It allows to exclude whole triggers.
In your case, the label should rather be
- wud.trigger.exclude=docker.autoupdate
If you want some containers to be pruned and some others not, then you need to create 2 different docker triggers (one with prune=true and the other one with prune=false) , and then associate the good one to each container.
N.B.
Setting wud.watch=false is making wud totally ignore them; is it really what you want to do?
Hi all,
Just installed WUD
How do I see the sensors in HA? I am tipping via MQTT somehow ?
Is there a guide?
You have to configure variables for WUD container, e.g. like that:
environment:
- WUD_TRIGGER_MQTT_MOSQUITTO_URL=mqtt://ip_address:1883
- WUD_TRIGGER_MQTT_MOSQUITTO_HASS_ENABLED=true
I’ve got mqtt working, but I don’t understand why the containers are missing so much data. It’s not pretty like in the doc.
Hi all, found this tool as I got sick of watchtower. I am trying to understand the docker compose auto update feature but I get stuck. I am running out of knowledge on this one so hopefully somebody can point me in the right direction.
I have setup two triggers (pushover and docker.compose), but I do get an error when I am trying to test run the docker.compose trigger.
Trigger executed with error (Error when running trigger dockercompose.update (Cannot destructure property 'dockerApi' of 'watcher' as it is undefined.)})
My docker-compose for WUD
whatsupdocker:
image: getwud/wud
container_name: wud
networks:
dockernation:
ipv4_address: 192.168.*.*
environment:
## Trigger PUSHOVER
- WUD_TRIGGER_PUSHOVER_NOTIFICATION_USER=****
- WUD_TRIGGER_PUSHOVER_NOTIFICATION_TOKEN=****
- WUD_TRIGGER_PUSHOVER_NOTIFICATION_HTML=1
## Trigger DOCKER-COMPOSE
- WUD_TRIGGER_DOCKERCOMPOSE_UPDATE_FILE=/docker-compose.yml
- WUD_TRIGGER_DOCKERCOMPOSE_UPDATE_BACKUP=true
- WUD_TRIGGER_DOCKERCOMPOSE_UPDATE_PRUNE=true
## Watcher LOCAL
- WUD_WATCHER_LOCAL_CRON=30 1 * * *
- WUD_WATCHER_LOCAL_WATCHALL=true
ports:
- 3000:3000
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /volume1/@docker/docker-compose.yml:/docker-compose.yml
- /volume1/docker/wud/store:/store
restart: always
anyone got an idea? @fmartinou sorry for tagging you but can you point me into the right direction?
I tested the same exact configuration as the one you provided and I don’t get your error. 
Can you try to force pull getwud/wud, maybe you’re not up-to-date?
(or switch to the latest release 8.0.1 to be sure)
To see if it fixes your issue…
1 Like
Thanks! I have updated to 8.0.0 and provided labels to my containers. I managed to start updating containers manually from the UI. This is great!!
That’s great! 
This is possible? How? Haven’t found it in the docu