-
Notifications
You must be signed in to change notification settings - Fork 913
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip updating containers where no local image info can be retrieved #612
Conversation
Won't this reintroduce #215 though? In the situation where the running container uses an image that it not available locally (anymore). |
It might very well do that, however - it will still grab What happens right now, is that all other calls to ImageInfo throughout the code will try to dereference a null pointer, and as a result, crashes watchtower. For instance: I think any suggestion as to how to do this differently is welcome, though, as relying on I'm holding off on approving this review until we've sorted out this discussion. 👍 |
21d7777
to
626ef9d
Compare
626ef9d
to
cc96db9
Compare
This will allow watchtower to continue even though the image info for a container cannot be retrieved. If this happens one warning will be emitted and the container will be skipped, unless NoRestart or OnlyMonitor is supplied
cc96db9
to
e735cc8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Partially reverts #571, since it causes
dockerClient.StartContainer()
to crash since it usesimageInfo
to rebuild the config.Fixes #584