containrrr / watchtower

A process for automating Docker container base image updates.
https://containrrr.dev/watchtower/
Apache License 2.0
18.6k stars 834 forks source link

Message "Waiting for running update to be finished..." after a server restart #2018

Open Daksol opened 3 weeks ago

Daksol commented 3 weeks ago

Describe the bug

Error message in logfile: "Waiting for running update to be finished..."

There was a previous discussion on this, now closed, #498

This appears in the Watchtower logfile after the server was restarted. The container check and update sequence ran a number of hours before, and finished without errors.

If I then do a docker compose restart the regular "Note that the first check.... " message appears, and situation is fine.

My situation not complicated - is there an easy way of embedding a 30 seconds startup delay to watchtower by adding some parameter to its docker-compose file?

Steps to reproduce

Restart server via sudo shutdown now -r

Expected behavior

I would expect to see the usual startup logfile entries from watchtower, like

watchtower-1  | time="2024-08-31T19:06:20+02:00" level=info msg="Watchtower 1.7.1"
watchtower-1  | time="2024-08-31T19:06:20+02:00" level=info msg="Using no notifications"
watchtower-1  | time="2024-08-31T19:06:20+02:00" level=info msg="Checking all containers (except explicitly disabled with label)"
watchtower-1  | time="2024-08-31T19:06:20+02:00" level=info msg="Scheduling first run: 2024-09-01 03:00:00 +0200 CEST"
watchtower-1  | time="2024-08-31T19:06:20+02:00" level=info msg="Note that the first check will be performed in 7 hours, 53 minutes, 39 seconds"

Screenshots

No response

Environment

Your logs

watchtower-1  | time="2024-08-31T18:53:56+02:00" level=info msg="Waiting for running update to be finished..."

Additional context

Occcurs after a server restart. Restarting the watchtower container fixes things.

github-actions[bot] commented 3 weeks ago

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! πŸ™