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
Right now when you stop the groundseg service, all of the auxiliary containers continue running. It would be nice to have some way to stop all the related containers, while keeping my other containers running. I propose stopping containers when the groundseg service is stopped, but some other way such as a command the user can issue would be ok too.
The text was updated successfully, but these errors were encountered:
We don't stop the containers when GS service is stopped because it would mean that your urbit shutdown whenever GS is updated and that is bad UX. I do think we should have a way to shutdown all containers
@mopfel-winrux
A thought: maybe it makes sense to bind systemctl restart groundseg and or systemctl reload groundseg to not stop the containers, but make systemctl stop groundseg stop them, and rewrite the update routines to use one of the first two commands
@neonfuz a little late to the convo but we need restart and stop to function the way it does now. This should be a CLI command though. Eg: groundseg stop-containers
Right now when you stop the groundseg service, all of the auxiliary containers continue running. It would be nice to have some way to stop all the related containers, while keeping my other containers running. I propose stopping containers when the groundseg service is stopped, but some other way such as a command the user can issue would be ok too.
The text was updated successfully, but these errors were encountered: