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
In these cases, kurtosis clean -a fails to kill them initially, but usually a second clean will kill them.
Desired behavior
kurtosis clean should always clean, regardless of zombie process or not. This might be looking for the "zombie process" message and attempting a retry, or maybe it's figuring out what's causing the thing to be a zombie process in the first place. Regardless, we should handle this for the user.
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
The text was updated successfully, but these errors were encountered:
## Description:
Hopefully fixes#959
It also adds a retry mechanism on RemoveContainer when this specific
error is hit
## Is this change user facing?
NO
<!-- If yes, please add the "user facing" label to the PR -->
<!-- If yes, don't forget to include docs changes where relevant -->
## References (if applicable):
<!-- Add relevant Github Issues, Discord threads, or other helpful
information. -->
What's your CLI version?
0.80.13
Description & steps to reproduce
For some reason, certain containers fail to die normally and are marked as zombies. We've seen this with NEAR, and also in HugoByte/DIVE#53 (comment) (even though the DIVE CLI is correctly using the "all" flag: https://github.com/HugoByte/DIVE/blob/main/cli/common/types.go#L201 )
In these cases,
kurtosis clean -a
fails to kill them initially, but usually a secondclean
will kill them.Desired behavior
kurtosis clean
should always clean, regardless of zombie process or not. This might be looking for the "zombie process" message and attempting a retry, or maybe it's figuring out what's causing the thing to be a zombie process in the first place. Regardless, we should handle this for the user.What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
The text was updated successfully, but these errors were encountered: