Docker: remove spawned containers after completion #2852
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Simone Tollardo <[email protected]>
tollsimy
force-pushed
the
fix/remove-build-containers
branch
from
01f1aad to
e7703e3
Compare
|
Not sure why the check |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similarly to #2843, remove spawned containers after completion.
Running containers using
kcitool results in dangling containers, which can lead to unnecessary disk space usage over time and leave the system in a dirty state.This PR updates the container run process to properly clean up containers after the execution is complete, preventing the accumulation of dangling containers.
This is evident when running some kbuilds, after which respective containers remains in exited state in the system.