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
Static IP doesn't work with with extra weavemesh network with IPAM driver #2046
Comments
Could you say which version of Weave you are using? If < 1.5.0 (which we haven't released yet) then this is fixed by #1916. |
I use weave:latest container and weave script from master branch. |
please post the output of |
weave script (unreleased version) |
|
Client: Server: |
But it's the same on coreos server with 1.10.2 as both server and client. |
reproduced (btw, there was a typo in the OP's instructions):
|
Ah, sorry, this got broken by #2012. The URL should be http://127.0.0.1:6784/ip/_/10.40.0.5/16 |
Steps to reproduce:
Result:
Expected result:
Container is created with 10.41.0.5 IP address attached.
Additional notes:
Assigning static IP works perfectly well when leaving default IPAM driver, but it doesn't maintain consistency across hosts (I can assing the same IP twice).
weavemesh
IPAM driver works only for defaultweave
network that launch-plugin creates.The text was updated successfully, but these errors were encountered: