deb Installation doesn't survive VM restart

[lachnerd]

Hi,

i'm using "docker-volume-vsphere" on some VMs running Ubuntu 16.04.2 LTS.

I installed them as follows:
sudo dpkg -i docker-volume-vsphere_0.12.3f64805_amd64.deb

Everythings working fine i see my vsphere Volumes and i'm able to use them etc.

But if i restart the VM vpshere support for docker is gone.

docker volume ls doesn't show me any vsphere volumes, i have to install the deb again although the installed files from it are still existing (for example "/usr/local/bin/docker-volume-vsphere")

So i have to install the docker-volume-vsphere everytime system reboots wich is pretty annoying.

Any tipps on that ?

[govint]

@lachnerd can you please post the file /var/log/docker-volume-vsphere.log from the VM thats showing this behavior. Post a restart the docker-volume-vsphere service should be available and can be checked either via "ps -ef|grep docker" or preferrably "service --status-all" and check the status of Docker and docker-volume-vsphere services.

[lachnerd]

Hi,

thanks for answering heres the Log File:
docker-volume-vsphere.zip

service --status-all shows me only a docker service but no "docker-volume-vsphere" service

But docker-volume-vsphere is working:

[msterin]

@lachnerd - reading through the message you seem to be doing the following steps (please confirm so we can try to reproduce and investigate) :

1. install docker (BTW - which version ?)
2. Install docker-volume-plugin Release 0.12 with dpkg -i command (no apt-get install -f was run)
3. checked that the plugin works (docker volume ls ,docker volume create work)
4. rebooted Ubuntu 16.04.2 LTS.
5. after reboot, docker volume ls does not show vsphere volumes (BTW - is there a delay in command output ?)
6. reinstalled the plugin with dpkg -i command
7. checked service --status-all - no plugin there
8. checked docker volume ls again and it worked.

Is it correct ? What steps are missing / were different ?

The plugin missing in service --status-all is a bug - we won't fix it since we are moving to Docker Managed Plugins anyways, and the current plan is to have in in 0.13 by the end of March. Meanwhile systemctl status docker-volume-vsphere can be used to check for the status

if you can send the results of journalctl -u docker it would help us to compare with internal test logs.

[lachnerd]

Hi,

1. OS: Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-62-generic x86_64) - Docker: Docker version 17.03.0-ce, build 3a232c8 - previously installed 1.13.1
2. yes - sudo dpkg -i docker-volume-vsphere_0.12.3f64805_amd64.deb
3. correct
4. correct
5. correct - and i noticed a delay from about maybe 20 s
6. correct
7. yes no volume plugin service only docker
8. yap

systemctl status docker-volume-vsphere result:

Results of journalctl -u docker:
docker-journal.zip

I tried to reproduce this on a brandnew ubuntu vm, installed 17.03.0-ce and tried to install the deb File and got an error:

Unfortunately its in german - it says that it can't be installed becaus of missing docker-engine - so i think youre forced to have a migrated system from docker-engine to docker 17.03.0-ce to install it.

[msterin]

@lachnerd - thanks for the info. The last issue you are hitting is #1023 . It is fixed in the master so if you build the .deb you'd get it fixed. Our current plan is to have 0.13 release around end of March and this will be fixed there too.

Unfortunately the original issue is caused by Docker in 1.13 API hanging if called before full initialization . We are changing out code to accommodate an will update the issue when the build is available