-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add a destroy
command to the wrapper script to support removing the currently running geodesic container
#798
Comments
I am inclined to close/refuse this request, because it seems to me to be a scary option, because it terminates all running shells without doing cleanup like saving shell history. You can specify a container by name in the Docker CLI, e.g.
which both seems to be easy enough to not warrant adding a separate Geodesic command and avoids Cloud Posse advocating or supporting such behavior. |
I like the option. And if it's scary, then default to a prompt =) Geodesic should be self-contained, and explaining other commands like calling |
@Gowiem @osterman I'm a little unclear about what you want. We recommend using the installed wrapper, which automatically removes the container image on termination, and has commands
If not using the installed wrapper, you can remove the container automatically with the If not using the installed wrapper and not using |
Describe the Feature
It would be great to have a
geodesic destroy
or similar command to remove the currently running image.Use Case
This would help in clearing the existing container in the case that the user no longer wants it around.
Describe Ideal Solution
geodesic destroy
would lookup the running geodesic container ID and issue adocker rm $CONTAINER_ID
against it.Alternatives Considered
N/A
Additional Context
N/A
The text was updated successfully, but these errors were encountered: