-
Notifications
You must be signed in to change notification settings - Fork 456
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
Update rmp
to test for running sandbox
#465
Conversation
cmd/crictl/sandbox.go
Outdated
if err != nil { | ||
return err | ||
} | ||
if !ctx.Bool("force") && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if force is true and sandbox state is READY, then invoke StopPodSandbox()
before RemovePodSandbox
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that sounds good, I will change it as adapted.
Running pod sandboxes have to be stopped before the actual removal. To achieve a better user-experience, we now error in that case and give the user the option to ignore it with the added `-f` flag for `rmp`. Signed-off-by: Sascha Grunert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feiskyer, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The CI has been passed from travis page, but didn't reflect the status from github hook. Merged this manually. |
Running pod sandboxes have to be stopped before the actual removal. To
achieve a better user-experience, we now error in that case and give the
user the option to ignore it with the added
-f
flag forrmp
.Closes #464