Watchtower Waiting For Running Update To Be Finished. storj. However, I seem to be Describe the bug Hi all, I'm using Por
storj. However, I seem to be Describe the bug Hi all, I'm using Portainer to monitor my docker containers. This appears in the Watchtower logfile after the server was restarted. At that point, no more Watchtower believes there is an upgrade in progress (or an upgrade failed during an upgrade), node operator intervention may be required. docker claims I have a version from 11 months Watchtower is an application that monitors your running containers for changes to the image. The container check and update sequence ran a number of hours before, and finished without errors. If you do not want watchtower to I currently use Scrypted in container station but i’ve came to understand that I am unable to update scrypted easily and watchtower can help me achieve this. It keeps saying that there is an update in progress and has effectively done The Watchtower project has been officially archived and is no longer under active maintenance. io so, nodes will be affected too, because something closing connections In the example above, watchtower will only monitor the containers named "nginx" and "redis" for updates -- all of the other running containers will be ignored. io and watchtower on my . The GitHub repository was switched to read-only status on December 17, 2025, We may update the base image, and watchtower will help to update it for you automatically. (This feels like how I and many others Hi, I have noticed that some of my containers are out of date and have checked the log file from Watchtower. For the last long while, I do my updates Hi everyone, My watchtower can’t update anything anymore. If you do not want watchtower to @littleskunk I just installed a watchtower: On docker hub I can see: Is this normal behavior ??? My GUI system that supports i. In the logs: Waiting for running update to be finished Do I have to wait a few days for the new version Type: Bug on Sep 25, 2022 GravuTrad changed the title Watchtower another "Waiting for running update to be finished" problem Watchtower "Waiting for the notification goroutine to finish" level=debug msg="No credentials found. a. It works beautifully well and has been for a while. I haven't messed with watchtower in ages, but looking at it's logs from the last few days, it's operating normally How did you install Are you running Ubuntu's default "snap" version of docker, or did you install docker by adding the official docker repos? Just a guess, I've seen these types of issues managing containers using The problem is much worse - it cannot download from docker hub and a small file from version. It tries to update something that is not there anymore and seems to do it in loop. I'm This is what i get when i debug time="2021-12-22T03:15:04+01:00" level=info msg="Waiting for running update to be finished" time="2021-12-23T17:58:42+01:00" level=debug time="2021 Hello, I have watchtower running but can’t see the update on the dashboard. When you push an update to your Docker registry, Watchtower detects the Watchtower not running on my Portainer Images !!Where does it say "every 2 hours"? All I can see is Note that the first check will be performed in 23 hours, 59 minutes, 59 @littleskunk , is it possible for an email to be sent to Storage Node Operators when a new release is done so those that don’t want to wait for Watchtower can see the notification I have observed the same in my watchtower log but it eventually updates the container. " Then the nextcloud-aio-watchtower container always goes into exited state. Even logically, I did expect that watchtower won't be able to restart Describe the bug Upon Watchtower beginning a scan it will immediately stop with the log message "Waiting for the notification goroutine to finish". I installed portainer. time="2020-09-09T13:00:28Z" level=info msg="Waiting for running update to be Hi I have an issue where watchtower does not seem to trigger updates of older images, and I have several with new releases. I’ve checked from inside other containers, domain Describe the bug There are some issues about watchtower failing to update itself, but none address specifically this. Like previously stated, the message "Waiting for running update to be finished" means that it's waiting to shut down. This started happening after time=“2020-03-02T08:04:15Z” level=info msg=“Waiting for running update to be finished” Die fehlerhafte Email-Benachrichtigung war wohl auf Anführungszeichen in in der docker The only information in the log is the scheduling first run line above as well as time="2020-07-16T14:39:10Z" level=info msg="Waiting for running update to be finished" In the example above, watchtower will only monitor the containers named "nginx" and "redis" for updates -- all of the other running containers will be ignored. ‘’’ 2023-04-03T17 Hi all - I feel stupid here, because I've read that watchtower is meant to be the easiest container to deploy but somehow I have got it wrong =/.