WATCHTOWER_NO_RESTART doesn't recreate containers after updating #1440
-
From the description of the argument here, https://containrrr.dev/watchtower/arguments/#without_restarting_containers It states that the "no restart" option doesn't restart the containers after updating. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
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. This means that the |
Beta Was this translation helpful? Give feedback.
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.