Correct Email Monitoring Config

[Enissay]

Hi,

I am using the config below and I was expecting daily emails with the list of containers to update (I guess), instead I am getting this so I am wondering if my config needs to be corrected:

Config snippet:

    image: containrrr/watchtower:latest
    environment:
      - WATCHTOWER_MONITOR_ONLY=true      # Due to Docker API limitations the latest image will still be pulled from the registry
      - WATCHTOWER_CLEANUP=true           # Removes old images after updating
      - TZ=Europe/Brussels
      - WATCHTOWER_INCLUDE_STOPPED=true
      - WATCHTOWER_INCLUDE_RESTARTING=true
      #####################################################################
      # Use Either SCHEDULE or INTERVAL (this last one in sec)
      # Cron help: https://crontab.guru/#0_0_8_*_*
      # cron: s | m | h | dom | m | dow
      - WATCHTOWER_SCHEDULE=0 0 8 * * *
      #- WATCHTOWER_POLL_INTERVAL=3000
      #####################################################################
      - WATCHTOWER_NOTIFICATIONS=email
      - [email protected]
      - [email protected],[email protected]
      - WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG=[DockerContainerUpdate]
      - [email protected]
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=xyz
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER=smtp.gmail.com
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=587
      - WATCHTOWER_NOTIFICATION_EMAIL_DELAY=30
      #####################################################################
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

Any idea what needs ot be adpated in order to get only info about which containers can be updated ?

[simskij]

Hi!

No, that is by design. Since DockerHub started to enforce rate limiting, we added support for doing HEAD requests to compare digests instead of pulling the whole manifest. We decided to put that as a warning as watchtower no longer doing head requests would mean their usage quota will be consumed.

[Enissay]

Okay, but those messages are vague:

• Does each line relate to one image/container ? or just same image spammed all this ?
• Which containers/images concerned ?
• Is there a way make this more explicit ? or is it hardcoded ?

[piksel]

Yeah, all good points. That information is displayed if debug is enabled, but just repeating the warning for every container without any context is definitely not helping anyone...

[Enissay]

That information is displayed if debug is enabled

According to my config above, Debug is not active I believe...
So basically this is the daily email I get, not very helpful indeed

[piksel]

Yeah, sorry, what I meant was that the information about why it happened is displayed if debug is enabled. It won't be sent in notifications anyway, unless WATCHTOWER_NOTIFICATIONS_LEVEL=debug is also set.