Unable to install vDVS managed plugin

[ashahi1]

Unable to install vDVS managed plugin due to following error:
Error response from daemon: dial unix /run/docker/plugins/1813c6b3d8e589b6d379ffc62665a1645a98e6a68cb4805ee2f082a1df5f4619/vsphere.sock: connect: no such file or directory

Steps:

1. Installed 0.15 plugin.
2. Created a volume
3. Ran a container with volume mounted
4. While container is running, removed the 0.15 plugin
5. Tried to install 0.16 plugin but installation failed

---

Detailed steps and their output are as follows:

root@promc-2n-dhcp105-23:~# docker plugin install --grant-all-permissions --alias vsphere vmware/docker-volume-vsphere:0.15
0.15: Pulling from vmware/docker-volume-vsphere
967f49dfadaf: Download complete
Digest: sha256:64a50830c2fa9befbede6efca3f28d2e2d8b4e595703f1b5984470579656e935
Status: Downloaded newer image for vmware/docker-volume-vsphere:0.15
Installed plugin vmware/docker-volume-vsphere:0.15
root@promc-2n-dhcp105-23:~#
root@promc-2n-dhcp105-23:~# docker plugin ls
ID                  NAME                DESCRIPTION                           ENABLED
549df37a8554        vsphere:latest      VMWare vSphere Docker Volume plugin   true
root@promc-2n-dhcp105-23:~#

2. Created a volume

root@promc-2n-dhcp105-23:~# docker volume create -d vsphere --name HelloWorldVol1
HelloWorldVol1
root@promc-2n-dhcp105-23:~#
root@promc-2n-dhcp105-23:~# docker volume ls
DRIVER              VOLUME NAME
vsphere:latest      HelloWorldVol1@local2
root@promc-2n-dhcp105-23:~#

3. Ran the container and mounted the volume

root@promc-2n-dhcp105-23:~# docker run -it --volume-driver=vsphere:latest -v HelloWorldVol1@local2:/vol1 --name ub_1 ubuntu
Unable to find image 'ubuntu:latest' locally
latest: Pulling from library/ubuntu
d5c6f90da05d: Pull complete
1300883d87d5: Pull complete
c220aa3cfc1b: Pull complete
2e9398f099dc: Pull complete
dc27a084064f: Pull complete
Digest: sha256:34471448724419596ca4e890496d375801de21b0e67b81a77fd6155ce001edad
Status: Downloaded newer image for ubuntu:latest
root@5260a60eee41:/# ls
bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var  vol1
root@5260a60eee41:/# echo "Hello" >> vol1/hello
root@5260a60eee41:/# echo "Hello World" >> vol1/hello
root@5260a60eee41:/# cat vol1/hello```

4. While container was running, removed 0.15 version and tried to install 0.16 version

root@promc-2n-dhcp105-23:~# docker plugin install --grant-all-permissions --alias vsphere16 vmware/docker-volume-vsphere:0.16
0.16: Pulling from vmware/docker-volume-vsphere
1d54a760dc2a: Download complete
Digest: sha256:5281d47506740ee927001ea5fc16d8584ed7fc04de0fb25969f0b11eb3243345
Status: Downloaded newer image for vmware/docker-volume-vsphere:0.16
Error response from daemon: dial unix /run/docker/plugins/1813c6b3d8e589b6d379ffc62665a1645a98e6a68cb4805ee2f082a1df5f4619/vsphere.sock: connect: no such file or directory
root@promc-2n-dhcp105-23:~#
root@promc-2n-dhcp105-23:~# docker plugin ls
ID                  NAME                DESCRIPTION                           ENABLED
1813c6b3d8e5        vsphere16:latest    VMWare vSphere Docker Volume plugin   false
root@promc-2n-dhcp105-23:~#
root@promc-2n-dhcp105-23:~# docker plugin enable 1813c6b3d8e5
Error response from daemon: dial unix /run/docker/plugins/1813c6b3d8e589b6d379ffc62665a1645a98e6a68cb4805ee2f082a1df5f4619/vsphere.sock: connect: no such file or directory
root@promc-2n-dhcp105-23:~# docker plugin ls
ID                  NAME                DESCRIPTION                           ENABLED
1813c6b3d8e5        vsphere16:latest    VMWare vSphere Docker Volume plugin   false

[govint]

Issue is very similar to moby issue 31723. Should open an issue on moby and reference this one.

[govint]

The issue doesn't happen every time that the plugin is installed, but repros when the plugin is installed and there are volumes in use and those need to be mounted as part of start up recovery.

[govint]

Given how install upgrade works for docker this issue used a set of steps thats known to not work. The correct approach is to only use docker plugin upgrade, which requires the plugin to be disabled and then upgraded.

I'm closing this issue as it need not be fixed unless issue repros otherwise.