{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/22708","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/22708/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/22708/comments","events_url":"https://api.github.com/repos/docker/docker/issues/22708/events","html_url":"https://github.com/docker/docker/issues/22708","id":154579617,"number":22708,"title":"plugins_volume.md: more information needed","user":{"login":"rck","id":42089,"avatar_url":"https://avatars.githubusercontent.com/u/42089?v=3","gravatar_id":"","url":"https://api.github.com/users/rck","html_url":"https://github.com/rck","followers_url":"https://api.github.com/users/rck/followers","following_url":"https://api.github.com/users/rck/following{/other_user}","gists_url":"https://api.github.com/users/rck/gists{/gist_id}","starred_url":"https://api.github.com/users/rck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rck/subscriptions","organizations_url":"https://api.github.com/users/rck/orgs","repos_url":"https://api.github.com/users/rck/repos","events_url":"https://api.github.com/users/rck/events{/privacy}","received_events_url":"https://api.github.com/users/rck/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-05-12T20:56:55Z","updated_at":"2016-05-18T08:30:41Z","closed_at":null,"body":"Hi fellow volume plugin developers!\r\n\r\nI'm currenty writing my first volume plugin and I have some questions that are not really answered in the API documentation. I will send a pull request that clarifies these points because I think it will also help others:\r\n\r\nOn .Create I create a special device, let's call it /dev/specialdev_name and put a file system on top of it.\r\nOn .Mount I mount it and reference count for the name. The first .Mount really mounts the file system, further .Mounts increase the refcount.\r\nOn .Umount I decrease the refcount and if 0, I umount the /dev/specialdev_name\r\nOn .Remove I remove the /dev/specialdev_name if the refcount is 0/is not mounted, otherwise I set Err.\r\n\r\nSo far so easy, the problem are .Path (and .Get and .List). To me it is not clear how to react if a volume is known to the driver (i.e., it was created with .Create), but is currently _not_ mounted. Should I report the \"Mountpoint\" where it will be available after a .Mount, or set \"Err\"? The same question applies for .Get. For .List it seams that I should include volumes known but not mounted, otherwise they don't show up in \"docker volume ls\". But yeah, it all boils down to this \"known to the plugin and created, but currently not mounted\" situation. Set Mountpoint to where it will be available after .Mount? Or set Mountpoint to \"\"? Or even set Err?\r\n"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/219960322","html_url":"https://github.com/docker/docker/issues/22708#issuecomment-219960322","issue_url":"https://api.github.com/repos/docker/docker/issues/22708","id":219960322,"user":{"login":"thaJeztah","id":1804568,"avatar_url":"https://avatars.githubusercontent.com/u/1804568?v=3","gravatar_id":"","url":"https://api.github.com/users/thaJeztah","html_url":"https://github.com/thaJeztah","followers_url":"https://api.github.com/users/thaJeztah/followers","following_url":"https://api.github.com/users/thaJeztah/following{/other_user}","gists_url":"https://api.github.com/users/thaJeztah/gists{/gist_id}","starred_url":"https://api.github.com/users/thaJeztah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thaJeztah/subscriptions","organizations_url":"https://api.github.com/users/thaJeztah/orgs","repos_url":"https://api.github.com/users/thaJeztah/repos","events_url":"https://api.github.com/users/thaJeztah/events{/privacy}","received_events_url":"https://api.github.com/users/thaJeztah/received_events","type":"User","site_admin":false},"created_at":"2016-05-18T08:30:41Z","updated_at":"2016-05-18T08:30:41Z","body":"@rck let's keep this open for tracking the documentation update; if you can refer to this issue with `fixes #22708` in your PR description, that will automatically close this issue once merged.\r\n\r\nThanks in advance!"}}