-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
docker engine fails to recognize managed plugin driver after uninstalling DEB package #32635
Comments
Just because user does a Also, user is creating an pluginv2 alias which conflicts with the pluginv1. This again results in expected pluginv2 discovery issues and get resolved with referencing the plugin with To transition between pluginv1 and pluginv2, users will need to restart engine. |
Thanks @anusha-ragunathan !
While using package installation (using deb/rpm), there is no issue at all. Volume creation failure or
Shouldn't |
No docker API will have that kind of privilege. |
When the v1 (unmanaged) plugin is removed, the .Sock file (and json if it was around) is removed. Methinks it's a good hint to remove the old driver from internal tracking without restart. At any rate, it's a doc update for us so it does not feel like a hi priority issue, |
Description
I was having docker-volume-vshere plugin, called as vDVS, using package based installation so far. Now the plugin is having support of Docker Managed plugin system, so uninstalled vDVS plugin (
dpkg -P docker-volume-vsphere
) and installed managed plugin by pulling from docker store (usingdocker plugin install --grant-all-permissions --alias vsphere vmware/docker-volume-vsphere:latest
).Following issues I have observed:
docker volume ls
takes more time to complete/responddocker volume ls
shows volume multiple entries for the same volume namedocker volume ls
pause for ~30 seconds and shows the output (shows volumes created previously).Further volume creation fails with following error.
docker volume ls
shows volume entries twice one for package based installation driver and another for managed plugin based installation driver ( see received result area for more detail)Steps to reproduce the issue:
Pre-reqs: VMWare ESX with a Docker host VM inside. (Ubuntu 16.04 Mini) and docker-volume-vsphere VIB installed.
See https://github.com/vmware/docker-volume-vsphere/ for more info
Downloads: https://github.com/vmware/docker-volume-vsphere/releases/tag/0.13
vsphere
and make sure volume is created successfullydocker plugin ls
to validate managed plugin installationDescribe the results you received:
docker.service log
Describe the results you expected:
Moving to managed plugin based installation should be transparent; either docker service should be restarted automatically as part of
docker plugin install
or call out explicitly if any extra steps needs to be done.As you can see, the plugin is installed using
--alias
keyword, so further volume creation should not be failed.Additional information you deem important (e.g. issue happens only occasionally):
Note: After restarting docker service, while invoking above command again works fine and
docker volume ls
also responds quickly.Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
/CC @msterin @pdhamdhere
The text was updated successfully, but these errors were encountered: