8000 Support subnet and iprange arguments on network create by bboreham · Pull Request #1915 · weaveworks/weave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jun 20, 2024. It is now read-only.

Support subnet and iprange arguments on network create #1915

Merged
merged 1 commit into from
Jan 22, 2016

Conversation

bboreham
Copy link
Contributor

Fixes #1806

It is perhaps cheating to get Docker to store the info we need, smuggled inside the pool name. But I don't see any reason why it should break.

ip.Mask = subnet.Mask // fix up the subnet we lied about
} else {
err = fmt.Errorf("Unrecognized pool ID: %s", poolID)
}

This comment was marked as abuse.

@bboreham bboreham force-pushed the issues/1806-plugin-subnet branch 4 times, most recently from 6a43ca9 to cc8af49 Compare January 22, 2016 12:26
@bboreham
Copy link
Contributor Author

Added documentation and squashed commits

@rade rade force-pushed the issues/1806-plugin-subnet branch from cc8af49 to 1a59734 Compare January 22, 2016 13:39
@rade rade added this to the 1.5.0 milestone Jan 22, 2016
rade added a commit that referenced this pull request Jan 22, 2016
Support subnet and iprange arguments on network create

Closes #1806.
@rade rade merged commit 83412e4 into master Jan 22, 2016
containers attached to them will be able to communicate with
containers attached to `weave`; there is no isolation between those
networks.
$ docker network create --driver=weavemesh --ipam-driver=weavemesh --subnet=<subnet> <network-name>

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@rade rade deleted the issues/1806-plugin-subnet branch March 19, 2016 16:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0