-
Notifications
You must be signed in to change notification settings - Fork 880
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
feature: pass IPAM options at docker run #2066
Comments
@greenpau we have this PR docker/cli#317 open few months back. We can try to put it on the fast track. |
@abhi , that would be nice 👍 |
@abhi , the interesting thing is in
|
Currently, when a user creates a network, the user can pass IPAM options via
--ipam-opt
.However, when a user creates a container, the user cannot pass IPAM options.
In conventional/traditional networking, e.g. DHCP, a request might contain the following options.
I suggest adding the ability to pass IPAM options at
docker run
and make sure that the options are passed all the way to/IpamDriver.RequestAddress
endpoint. This way IPAM plugin would be capable of passing a lot more information to remote IPAM servers for the servers to make IP address management decisions.For example,
--ipam-opt vnid=<id>
would allow IPAM driver to notify that the IP address request have VXLAN identifier associated with it. The IPAM servers would then use that information for routing purposes.The text was updated successfully, but these errors were encountered: