dockercompose trigger does not work

[Skullchuck]

Hi all,

I'm new to WUD. I set up a notification trigger, which works perfectly. Now I wanted to add a dockercompose trigger to update my adguardhome container. Unfortunately, the trigger does not update the container. In detail, I can see it's able to rewrite the docker compose file, but then it seems to be unable to pull an image.

Details:

Host system:
Openmediavault 6.9.16-1 (Shaitan) / Linux 6.1.0-0.deb11.21-amd64

Log message from wud container:

whats-up-docker/container: Trigger executed with success
type=dockercompose,
name=adguardhome,
container={
"id":"ceef890b378c98a30d32a1d0da85104b125eec63e45a434a6ba78a404102f6af",
"name":"adguardhome",
"status":"running",
"watcher":"local",
"displayName":"adguardhome",
"displayIcon":"mdi:docker",
"triggerInclude":"smtp.yahoo,dockercompose.adguardhome",
"image":{"id":"sha256:9f4ef14c247b96b97d0ab42f3101528b466111dac41eee1224b564ab9722e178",
"registry":{"url":"https://registry-1.docker.io/v2",
"name":"hub.public"
},
"name":"adguard/adguardhome", "tag":{"value":"latest","semver":false},
"digest":{"watch":true,"repo":"sha256:b04764acecf1f663a23f55e95724a3c7ca0dc7f3a6f957d29005728b6bd036f2","value":"sha256:7e05245ac1e9c54ff10e4d994783ab340f69b3b727f75a1a90e9808b978552d5"},
"architecture":"amd64",
"os":"linux",
created":"2025-05-27T12:02:23.049Z"}, "labels":{
"com.docker.compose.config-hash":"fd2ff0a0f4cb3cf5727db1cd09864eff4b49984b7fc7969b06de4b625c6bd969",
"com.docker.compose.container-number":"1",
"com.docker.compose.depends_on":"",
"com.docker.compose.image":"sha256:9f4ef14c247b96b97d0ab42f3101528b466111dac41eee1224b564ab9722e178",
"com.docker.compose.oneoff":"False",
"com.docker.compose.project":"adguardhome",
"com.docker.compose.project.config_files":"/srv/dev-disk-by-uuid-/users//docker/adguardhome/docker-compose.yml",
"com.docker.compose.project.working_dir":"/srv/dev-disk-by-uuid-/users//docker/adguardhome",
"com.docker.compose.service":"adguardhome",
"com.docker.compose.version":"2.29.2",
"maintainer":"AdGuard Team devteam@adguard.com",
"org.opencontainers.image.authors":"AdGuard Team devteam@adguard.com",
"org.opencontainers.image.created":"2025-05-27T12:02:16Z",
"org.opencontainers.image.description":"Network-wide ads & trackers blocking DNS server",
"org.opencontainers.image.documentation":"https://github.com/AdguardTeam/AdGuardHome/wiki/",
"org.opencontainers.image.licenses":"GPL-3.0",
"org.opencontainers.image.revision":"5076ec028a7d3ce23bcb953cebf7a387ab4cf9be",
"org.opencontainers.image.source":"https://github.com/AdguardTeam/AdGuardHome",
"org.opencontainers.image.title":"AdGuard Home",
"org.opencontainers.image.url":"https://adguard.com/en/adguard-home/overview.html",
"org.opencontainers.image.vendor":"AdGuard",
"org.opencontainers.image.version":"v0.107.62",
"wud.trigger.include":"smtp.yahoo,dockercompose.adguardhome"
},
"updateAvailable":true, "updateKind":{
"kind":"digest",
"localValue":"sha256:7e05245ac1e9c54ff10e4d994783ab340f69b3b727f75a1a90e9808b978552d5",
"remoteValue":"sha256:4d9df912d614dc8d723e3db99b75985e48fc841b303f3247810248519c6ce05a"
},
"result":{
"tag":"latest",
"digest":"sha256:4d9df912d614dc8d723e3db99b75985e48fc841b303f3247810248519c6ce05a"
}
}
)

Docker-compsoe file of the WUD container:

services:
whatsupdocker:
image: getwud/wud
container_name: wud
environment:
- PGID=993
- WUD_WATCHER_LOCAL_CRON=15 8 * * *
- WUD_AUTH_BASIC_MY_USER=[...]
- WUD_AUTH_BASIC_MY_HASH=[...]
[...]
- WUD_TRIGGER_DOCKERCOMPOSE_ADGUARDHOME_FILE=/wud/adguardhome/docker-compose.yml
- WUD_TRIGGER_DOCKERCOMPOSE_ADGUARDHOME_PRUNE=true
- WUD_TRIGGER_DOCKERCOMPOSE_ADGUARDHOME_AUTO=false
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /srv/dev-disk-by-uuid-[UUID]/users/[USER]/docker/adguardhome/docker-compose.yml:/wud/adguardhome/docker-compose.yml
ports:
- 3000:3000

Labels in the docker-compose file of the adguardhome container:
labels: wud.trigger.include: smtp.yahoo,dockercompose.adguardhome

Nothing relevant shows up in the docker host log.

Failed solution approach

I guessed that something with the permissions of the docker.sock was wrong, but this does not seem to be the case. First, I added the WUD container to the docker group (PGID 993, see above), which already had read&write permissions on the docker.sock. This didn't help – eventually I allowed read&write access to others on the docker.sock. Unfortunately, this did not solve the issue, either.

Any idea, anyone? Thank you!

Cheers

[luisangelico]

Same issue here

[david-uhlig]

I had the same issue. My compose.yaml looked something like this

services:
  busybox:
    image: busybox
    labels:
      wud.watch: true
      wud.watch.digest: true
      wud.tag.include: latest

Note the omitted latest tag on the image, which is perfectly valid and resolves automatically to latest in docker compose. However, when WUD scans the compose.yaml it looks for a match on the image attribute for busybox:latest explicitly. As it doesn't find it, it skips the auto updating process.

The temporary solution is to explicitly add the latest tag, such that your compose.yaml looks like this:

services:
  busybox:
    image: busybox:latest
    labels:
      wud.watch: true
      wud.watch.digest: true
      wud.tag.include: latest

Let me know if that works for you. I'll post a bug report later on. Cheers.

[luisangelico]

should I do this in wud compose file or immich (app that I want to wud)?

[david-uhlig]

You would do this in the compose file of the image that you want WUD to update. In your case, immich.

[Skullchuck]

@david-uhlig yes, that was it! Now it's working. Thank you very much