You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems, that the variable --notification-email-delay (or the environment variable WATCHTOWER_NOTIFICATION_EMAIL_DELAY) is ignored and the email is send immediately after finishing the update process of all containers.
This is a problem, when the mail service itself is a docker service and updated by watchtower and not yet ready to receive the email from watchtower. To Reproduce
and fill the variables with correct data
2. Wait until watchtower starts at midnight and new container are available for updates
3. Email will be send immediately
Expected behavior
After updating the container(s) the email notification should not be sent before 00:05 a.m. (300s = 5 minutes)
Screenshots
Environment
Platform: Debian Bullseye (Linux 5.10.17-v8+)
Architecture: aarch64 (Raspberry Pi)
Docker version: Docker version 20.10.9, build c2ea9bc
Logs from running watchtower with the --debug option
The logs are a little bit old, but the bug exists from beginning and i logged the debug output in July.
Container beginning with "mailu" are updated and mailu is the mail service that should receive the message from watchtower.
After finishing watchtower tries to send the mail (i removed the real address from the log), but since the containers are not ready yet the notification is failing.
The text was updated successfully, but these errors were encountered:
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏
Describe the bug
It seems, that the variable
--notification-email-delay
(or the environment variableWATCHTOWER_NOTIFICATION_EMAIL_DELAY
) is ignored and the email is send immediately after finishing the update process of all containers.This is a problem, when the mail service itself is a docker service and updated by watchtower and not yet ready to receive the email from watchtower.
To Reproduce
and fill the variables with correct data
2. Wait until watchtower starts at midnight and new container are available for updates
3. Email will be send immediately
Expected behavior
After updating the container(s) the email notification should not be sent before 00:05 a.m. (300s = 5 minutes)
Screenshots
Environment
Debian Bullseye (Linux 5.10.17-v8+)
aarch64 (Raspberry Pi)
Docker version 20.10.9, build c2ea9bc
Logs from running watchtower with the
--debug
optionAdditional context
The logs are a little bit old, but the bug exists from beginning and i logged the debug output in July.
Container beginning with "mailu" are updated and mailu is the mail service that should receive the message from watchtower.
After finishing watchtower tries to send the mail (i removed the real address from the log), but since the containers are not ready yet the notification is failing.
The text was updated successfully, but these errors were encountered: