Skip to content

Vendoring libnetwork to address some concurrency issues#28975

Merged
LK4D4 merged 1 commit intomoby:masterfrom
mavenugo:ln113
Nov 30, 2016
Merged

Vendoring libnetwork to address some concurrency issues#28975
LK4D4 merged 1 commit intomoby:masterfrom
mavenugo:ln113

Conversation

@mavenugo
Copy link
Contributor

@mavenugo mavenugo commented Nov 30, 2016

Fixes #28697, #28712, #28559, #26111

Signed-off-by: Madhu Venugopal [email protected]

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

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

LGTM 🐸
/cc @vieux

@mavenugo
Copy link
Contributor Author

updated vendoring with a fix for #26111

@tonistiigi
Copy link
Member

LGTM

1 similar comment
@LK4D4
Copy link
Contributor

LK4D4 commented Nov 30, 2016

LGTM

@LK4D4
Copy link
Contributor

LK4D4 commented Nov 30, 2016

experimental looks flaky
#28987

@LK4D4
Copy link
Contributor

LK4D4 commented Nov 30, 2016

I'm going to merge anyway.

@matevarga
Copy link

matevarga commented Nov 11, 2019

By the way, this is not fixed. docker-compose up on a compose file with >100 containers will result in routes not set up properly and containers not being able to communicate with each other. "experimental looks flaky -- I'm going to merge anyway." is not a great approach when fixing concurrency issues in my opinion.
(I know this is an OSS project, but we do pay for Docker, quite a lot.)

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.

[1.12.3] Swarm node crash "fatal error: concurrent map read and map write"

7 participants