Skip to content

WATCHTOWER_NO_RESTART doesn't recreate containers after updating #1440

Answered by piksel
milindpatel63 asked this question in General
Discussion options

You must be logged in to vote

Yeah, the way it works now doesn't make any sense. I think this is a feature that has been broken by refactoring some time ago.
Currently the StartContainer call is the one that creates the new container, and then starts it.

This means that the no-restart option currently only removes containers which I cannot image is what anyone wants.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by simskij
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants