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
I've a production docker stack with ~70 containers.
I'm happy to see the #346 pull which provide the provider.auto-stop-on-startup option.
Now, I can confirm, my sablier supervised containers are shut down by sablier after its start.
But, if I do a docker compose up -d on my docker stack, and there is no update on sablier. The sablier container is not restarted, my containers are all started (especially the ones that were shut down by sablier).
Does sablier shut down the containers again? Or will it wait for the configured time?
Or do I've to make a first request like before for sablier to decide to start the timer?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey everyone,
I've a production docker stack with ~70 containers.
I'm happy to see the #346 pull which provide the
provider.auto-stop-on-startup
option.Now, I can confirm, my sablier supervised containers are shut down by sablier after its start.
But, if I do a
docker compose up -d
on my docker stack, and there is no update on sablier. The sablier container is not restarted, my containers are all started (especially the ones that were shut down by sablier).Does sablier shut down the containers again? Or will it wait for the configured time?
Or do I've to make a first request like before for sablier to decide to start the timer?
Thanks !
Beta Was this translation helpful? Give feedback.
All reactions