You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, i noticed, that igm always deploys watchtower alongside the rest of the stack. The way it is done has a few problems/inconveniences.
So for example, if i dont want to do automatic updates, i have to disable/stop watchtower always again after deploying the stack.
Also if i have already a deployed watchtower container, this could result in problems (it might, its not guranteed).
So in my opinion, one should be possible to disable deploying watchtower automtically (i havent found an option for that). Otherwise, watchtower should be deployed with the option to ONLY update the igm stack containers. This is possible by starting watchtower with the names of the containers it should update. Example from their wiki:
Hey, i noticed, that igm always deploys watchtower alongside the rest of the stack. The way it is done has a few problems/inconveniences.
So for example, if i dont want to do automatic updates, i have to disable/stop watchtower always again after deploying the stack.
Also if i have already a deployed watchtower container, this could result in problems (it might, its not guranteed).
So in my opinion, one should be possible to disable deploying watchtower automtically (i havent found an option for that). Otherwise, watchtower should be deployed with the option to ONLY update the igm stack containers. This is possible by starting watchtower with the names of the containers it should update. Example from their wiki:
The text was updated successfully, but these errors were encountered: