Skip to content
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

[19.03 backport] allocateNetwork: fix network sandbox not cleaned up on failure #41081

Merged

Conversation

thaJeztah
Copy link
Member

partial backport (only the first commit) of #41020

The defer function was checking for the local err variable, not on the error that was returned by the function. As a result, the sandbox would never be cleaned up for containers that used "none" networking, and a failiure occured during setup.

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

The defer function was checking for the local `err` variable, not
on the error that was returned by the function. As a result, the
sandbox would never be cleaned up for containers that used "none"
networking, and a failiure occured during setup.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit b98b8df)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@tiborvass
Copy link
Contributor

2s timeout in TestDaemonDNSFallback might be too little for ppc64

Copy link
Member

@cpuguy83 cpuguy83 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah thaJeztah modified the milestones: 19.03.12, 19.03.13 Jun 30, 2020
@AkihiroSuda AkihiroSuda merged commit 2d4bfdc into moby:19.03 Jul 26, 2020
@thaJeztah thaJeztah deleted the 19.03_backport_fix_sandbox_cleanup branch July 26, 2020 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants