getwud / wud

WUD (aka What's up Docker?) gets you notified when a new version of your Docker Container is available.
https://getwud.github.io/wud/
MIT License
1.22k stars 39 forks source link

Remote Docker Host not monitored #387

Open marcolino7 opened 6 months ago

marcolino7 commented 6 months ago

Hi, I have 3 docker host in my homelab. One of them run WUD, and accessed via local file. Other two are accessed via tcp socket without encryption. Here is config:

version: '3'
services:
  whatsupdocker:
    image: fmartinou/whats-up-docker
    container_name: Whats-Up-Docker
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /volume1/docker/whats-up-docker:/store
    ports:
      - 3000:3000
    environment:
      - TZ=Europe/Rome
      - WUD_WATCHER_SYNOLOGY_SOCKET=/var/run/docker.sock
      - WUD_WATCHER_SYNOLOGY_CRON=10 9 * * *
      - WUD_WATCHER_DOCKER1_HOST=192.168.99.74
      - WUD_WATCHER_DOCKER1_CRON=11 9 * * *
      - WUD_WATCHER_SURVIVAL_HOST=192.168.99.63
      - WUD_WATCHER_SURVIVAL_CRON=12 9 * * *
      - WUD_TRIGGER_PUSHOVER_1_TOKEN=------MY TOKEN------
      - WUD_TRIGGER_PUSHOVER_1_USER=--------MY USER--------
      - WUD_TRIGGER_PUSHOVER_1_SIMPLEBODY=Container $${name} running on $${watcher} have an update available \n
      - WUD_TRIGGER_PUSHOVER_1_PRIORITY=0
      - WUD_TRIGGER_PUSHOVER_1_MODE=batch
      - WUD_TRIGGER_PUSHOVER_1_ONCE=false

When Cron start, I receive notification on SYNOLOGY, the docker.sock one. On other 2 host, there is container that have not an image in docker Hob and raise an error, but other valid container are not checked:

09:10:00.848  INFO whats-up-docker/watcher.docker.synology: Cron started (10 9 * * *)
09:10:05.644  INFO whats-up-docker/watcher.docker.synology: Cron finished (17 containers watched, 0 errors, 3 available updates)
09:11:00.919  INFO whats-up-docker/watcher.docker.docker1: Cron started (11 9 * * *)
09:11:00.940  WARN whats-up-docker: docker1_SQLServer - No Registry Provider found
09:11:00.945  WARN whats-up-docker/watcher.docker.docker1: Error when processing (Unsupported Registry unknown) (container=docker1_SQLServer)
09:11:00.946  WARN whats-up-docker/watcher.docker.docker1: Error when processing some containers (Cannot read properties of undefined (reading 'tag'))
09:11:00.946  INFO whats-up-docker/watcher.docker.docker1: Cron finished (0 containers watched, 0 errors, 0 available updates)
09:12:00.949  INFO whats-up-docker/watcher.docker.survival: Cron started (12 9 * * *)
09:12:01.646  WARN whats-up-docker/watcher.docker.survival: Error when processing (401 - {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"library/docker-apcupsd","Action":"pull"}]}]}) (container=survival_docker-apcupsd-UPS1)
09:12:01.647  WARN whats-up-docker/watcher.docker.survival: Error when processing some containers (Cannot read properties of undefined (reading 'tag'))
09:12:01.647  INFO whats-up-docker/watcher.docker.survival: Cron finished (0 containers watched, 0 errors, 0 available updates)

On host docker1 there are container with valid image on dockerhub, but i get.docker1: Cron finished (0 containers watched, 0 errors, 0 available updates), and also for host survival.

I hope I miss something, but I cannot understand what.

Thanks in advance

Marco

cryptogeek13 commented 1 month ago

those error messages, especially the authorized part, read to me like your remote docker daemon requires authentication. Are you sure, you set that up correctly without encryption on your remotes?

Can you connect using docker -H=192.168.99.74:2376 version ?

Also the default port set by WUD is 2375, did you setup your docker remotes on this port, too? The docker documentation recommends port 2376, that's why I'm asking.