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
Similar to how services are started in a specific order (using 'start-after'), would it be possible to shutdown services in a specific order as well? Maybe even just in the reverse order that the services were started?
My use case is that I run a VPN (Tailscale), logs collector (Grafana Agent) and an API in the same container. When a shutdown occurs, ideally the API would shutdown first, then the logs collector, then the VPN. But currently, since the signal is sent to all services at once, the order is fairly random.
The text was updated successfully, but these errors were encountered:
Similar to how services are started in a specific order (using 'start-after'), would it be possible to shutdown services in a specific order as well? Maybe even just in the reverse order that the services were started?
My use case is that I run a VPN (Tailscale), logs collector (Grafana Agent) and an API in the same container. When a shutdown occurs, ideally the API would shutdown first, then the logs collector, then the VPN. But currently, since the signal is sent to all services at once, the order is fairly random.
The text was updated successfully, but these errors were encountered: