-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
halt/stop command #298
Comments
Noting that this could be implemented via #304 and something similar to |
For the CLI use case Tart was designed to not have a daemon running somewhere. This way consumers are responsible for killing tart process which will gracefully shutdown the VM. Hopefully vagrant can track own a process between |
hmmm it's not necessarily that a tart service or daemon needs to sit and actively monitor running VMs, though that is one way of doing it. Rather that vagrant itself is not a long running task. If Tart doesn't have some notes somewhere saying VM 1 is turned on with this PID then that means that running a command such as The downside of doing the housekeeping locally is that you then have to double check Tart exited gracefully and that the PID didn't get reused for something else. |
Confirmed that you can SSH into a tart Linux VM and run Tart will show:
It does require passwords entering but that's a configuration issue to add passwordless sudo. |
The remaining problem is that it's not possible to do this simple set of commands if a vagrant provider was built: # turn it on:
vagrant up <-- this command would never exit
# turn it off:
vagrant halt |
@tomjn something which came to mind: could the vagrant tart plugin spawn a child process when running |
@ringods theoretically, but that then leaves 2 new problems:
|
Closing because this has been resolved by #316. |
Currently you can execute
tart run
however there is no way to stop this VM via a command either in the current shell or in another shell on the same system. It's also unclear how you would track the current status of the VM wether it was running or idle.So, in addition to
tart run
, it would be nice to have atart stop
similar tovagrant halt
. This would send a shutdown signal to the VM requesting it powerdown/exit gracefully. Ideally an additional parameter could be provided for a more forceful/bruteforce termination of the VM processThe text was updated successfully, but these errors were encountered: