-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[release-1.19] Revert "runtime_vm: Cleanup process when the Container is Stopped" #4143
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
Conversation
This reverts commit 814c1bb. We cannot simply delete the container when its status changes to stopped. The intention of this fix is okay-ish, but implemented in the wrong layer. What containerd does is calling Shutdown(), when the *pod* is finished, and that's what we should do as well. Signed-off-by: Fabiano Fidêncio <[email protected]>
Codecov Report
@@ Coverage Diff @@
## release-1.19 #4143 +/- ##
================================================
+ Coverage 41.58% 41.60% +0.01%
================================================
Files 110 110
Lines 9046 9043 -3
================================================
Hits 3762 3762
+ Misses 4944 4941 -3
Partials 340 340 |
|
/lgtm |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fidencio, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/test e2e_features_fedora |
|
/test e2e-aws |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This reverts commit 814c1bb.
We cannot simply delete the container when its status changes to
stopped. The intention of this fix is okay-ish, but implemented in the
wrong layer.
What containerd does is calling Shutdown(), when the pod is finished,
and that's what we should do as well.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?