-
Notifications
You must be signed in to change notification settings - Fork 95
Docker does not send umount after mount failure. #320
Comments
We confirmed Docker indeed sends unmount request for failed mounts on more than one setup. Ritesh is going to give this a try on clean environment. Will re-open or file a new issue if we see this again. |
This is a bug in docker. if -w is passed during run, internally docker does not clean up (send unmount).
Logs for bug during failure ( includes docker and plugin logs)
|
Will search existing bugs if one is not filed will open a issue with docker. |
Opened moby/moby#22564 |
This is a Docker issue and not a TP blocker. User can workaround this issue by either skipping -w or using |
CC @govint |
Behavior is the same with Docker 1.12, First time, docker reaches to the plugin to mount the disk, it fails. Thereafter docker runs the container creating a folder on the local host FS and starts the container with the given working dir. The plugin has reference counted already the volume and won't let the volume to be removed. A restart of the plugin is what it takes to clear up the issue. $ docker run --rm -it -w /data -v newvol156:/data busybox $ docker volume rm newvol156 $ sudo service docker-volume-vsphere restart docker-volume-vsphere stop/waiting $ docker volume rm newvol156 I'll check if Docker is planning on fixing this or will try submitting a change to docker issue #22564 |
Creating a new issue for the plugin, Docker is fixing this with a change to never send an unmount for a failed mount (docker PR 27116). Closing this issue. |
Using this issue to track the work we need to do once Docker releases moby/moby#27116 |
Closing as #608 will address changes to the plugin to handle new docker behavior on mount failure. |
We need to check with docker for the behavior of the engine on mount failures.
There seems to be relevant discussion here: https://github.com/docker/docker/pull/21015/files
This issue is to follow up with Docker and figure out the right recovery of refcount status after mount failure.
The text was updated successfully, but these errors were encountered: