Steps to reproduce:
1./ Create the volume docker volume create --driver=vfile --name=test@datastore2 -o size=1gb
2./ Start a container, mounting the volume docker run --rm -it -v test@datastore2:/mnt/myvol --name busybox-on-node1 busybox
Expected result:
Container starts with volume mounted.
Actual result:
Get error docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/a0e758baa4e3022def1cb2893b8e27876158803a5fd8c2dd68697f60cebf7fc8/rootfs/mnt/vfile/test@datastore2': VolumeDriver.Mount: Timeout reached; BlockingWait is not complete.
Environment: ESX 6.0U3 Docker 17.09.1-ce Host OS: RancherOS 1.3.0
Steps to reproduce: 1./ Create the volume
docker volume create --driver=vfile --name=test@datastore2 -o size=1gb
2./ Start a container, mounting the volumedocker run --rm -it -v test@datastore2:/mnt/myvol --name busybox-on-node1 busybox
Expected result: Container starts with volume mounted.
Actual result: Get error
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/a0e758baa4e3022def1cb2893b8e27876158803a5fd8c2dd68697f60cebf7fc8/rootfs/mnt/vfile/test@datastore2': VolumeDriver.Mount: Timeout reached; BlockingWait is not complete.
I have plenty of space on the server but I tried increasing the timeout anyway (as per https://vmware.github.io/vsphere-storage-for-docker/documentation/vfile-plugin.html#i-got--volumedrivermount-failed-to-blocking-wait-for-mounted-state-error-timeout-reached-blockingwait-is-not-complete-when-mounting-a-volume ), but the error remained.
Note that it does work if I do not specify the datastore.
Relevant logs (from
/var/log/vfile/log
):