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

[Daksol]

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

• Platform Ubuntu Server 24.04 LTS
• Architecture AMD64
• Docker Version 27.2
• Watchtower version 1.71

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]

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! 🙏

[Daksol]

FWIW I have put in a work-round which seems to avoid the stated problem of the container never restarting after a Server restart.

I added an extra section to the Watchtower service in its Docker compose file, as below. This introduces a 30 second delay to Watchtower whenever the contaier restarts. This change now seems to ensure a successful restart.

    deploy:
        restart_policy:
            condition: any
            delay: 30s
            window: 60s