This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
Fixed docker0 address conflict #209
Open
Conversation
This file contains 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
Changed default netowork of host-only adapter to 172.19.8.*, actually any one other than 172.17.8.* works.
|
👍 |
|
Haven't seen this PR merged. Is there any concern about it? |
added 13 commits
August 9, 2015 13:29
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
docker0 default uses 172.17.42.1/16, so setting address of host-only adapter to 172.17.8.* leads to conflict, and makes docker0 picking other address (usually 10.1.42.1).
Solution
Changed default network of host-only adapter to 172.19.8.* (the next prime number, just my preference), actually any private network other than 172.17.1.1/16 works.
This may solve #82, #111, and #174.