Windows: don't try to load "mirrored" network plugin #50155
Merged
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.
- What I did
On my Windows laptop, I have some networks with type "mirrored" ...
On startup, Docker tries to adopt all of the networks it learns about from HNS. But "mirrored" isn't a supported network type, so it tries to load a network plugin called "mirrored". That doesn't exist, so it tries again after 1, 2, 4 and 8 seconds - per network (so, a minute's startup delay in total).
- How I did it
Don't try to load plugin "mirrored".
- How to verify it
Dockerd starts up quickly when the host has "mirrored" networks.
- Human readable description for the release notes