[20.10 backport] builder: ensure libnetwork state file do not leak#41972
Merged
Conversation
Member
Author
|
@tonistiigi @AkihiroSuda ptal |
Signed-off-by: Tonis Tiigi <[email protected]> (cherry picked from commit 7c7e168) Signed-off-by: Sebastiaan van Stijn <[email protected]>
thaJeztah
force-pushed
the
20.10_backport_net_leak_fix
branch
from
February 17, 2021 20:21
969632b to
e375035
Compare
Member
Author
|
rebased to trigger CI with test-fixes that were merged |
tiborvass
approved these changes
Feb 18, 2021
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
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.
backport of #41863
Cherry-pick was not clean, but only a minor issue; same (but reverse) as #41965 (comment)