-
Notifications
You must be signed in to change notification settings - Fork 878
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
Error in Docker Managed IPAM Plugin #1772
Comments
After Restarting the docker engine and creating network again
|
Looks like issue is with the code here
socketpaths list has two paths for the socket 1)
|
Looks like issue in Moby. Raised the same issue in moby/moby#33347 |
@ishantt I think we determined the solution for this in Docker Community slack a couple days ago. I've been able to use your plugin fine, and I think the issue was not specifying the full "ishant8/sdip:latest" in the --ipam-driver. Can this be closed? |
@eyz yes using full name "ishant8/sdip:latest" worked. I was again and again trying to create with the name "ishant8/sdip" as given in docs ( https://docs.docker.com/engine/extend/#installing-and-using-a-plugin ) and it was failing. Maybe this needs a doc change. Anyways I am happy to close this . |
The commit contains fix for the issue reported in moby/moby#33415 and moby#1772. With the feature introduced to support local scope networks in swarm mode the network configuration to include ipam driver was overriden in libnetwork. This has been removed with this fix which will allow ipam-driver option to be used for task allocation Signed-off-by: Abhinandan Prativadi <abhi@docker.com>
The commit contains fix for the issue reported in moby/moby#33415 and #1772. With the feature introduced to support local scope networks in swarm mode the network configuration to include ipam driver was overriden in libnetwork. This has been removed with this fix which will allow ipam-driver option to be used for task allocation Signed-off-by: Abhinandan Prativadi <abhi@docker.com>
The commit contains fix for the issue reported in moby/moby#33415 and #1772. With the feature introduced to support local scope networks in swarm mode the network configuration to include ipam driver was overriden in libnetwork. This has been removed with this fix which will allow ipam-driver option to be used for task allocation Signed-off-by: Abhinandan Prativadi <abhi@docker.com> (cherry picked from commit 21553c8) Signed-off-by: Tibor Vass <tibor@docker.com>
The commit contains fix for the issue reported in moby#33415 and moby/libnetwork#1772. With the feature introduced to support local scope networks in swarm mode the network configuration to include ipam driver was overriden in libnetwork. This has been removed with this fix which will allow ipam-driver option to be used for task allocation Signed-off-by: Abhinandan Prativadi <abhi@docker.com>
I have created a sample docker IPAM plugin to test the plugin interface. https://github.com/ishantt/docker-ipam-plugin .This works fine if I run in legacy mode i.e. spawning a external container. But If a create a Docker Managed plugin (v2 plugin) then it gives error .
dial unix /run/docker/plugins/sdip.sock: connect: no such file or directory
On docker Host
Steps to reproduce:
Docker Version:
docker info:
The text was updated successfully, but these errors were encountered: