Hi Shuai >From the link below, I pulled out changes needed while invoking docker cli or >docker api. This documentation is quite comprehensive and should tell what >changes are needed.
https://github.com/docker/docker/pull/13161 …….. $ docker run -ti -v volumename:/data --volume-driver=flocker busy box sh There is similar api change needed .. ………….. Adding this plugin into Mesos would give all necessary storage extensions needed for Mesos/Marathon. Can we discuss to support this out? Thanks On 6/6/15, 7:51 PM, "Shuai Lin" <linshuai2...@gmail.com<mailto:linshuai2...@gmail.com>> wrote: Hi Khanduja, What I understand the slave code which calls in docker cli would need this additional parameter to be passed into. I don't think mesos slave invokes docker cli directly. It calls the docker api instead. Also Is there any official documentation/introduction to docker plugin or volume extensions? I found the following two pages when googling, but non of them has an official introduction to volume extension. https://clusterhq.com/2014/12/08/docker-extensions/ https://github.com/docker/docker/pull/13161 Best Regards, Shuai On Sat, Jun 6, 2015 at 12:56 AM, Khanduja, Vaibhav <vaibhav.khand...@emc.com<mailto:vaibhav.khand...@emc.com> wrote: Recently docker pulled in code for supporting docker volume extensions. The docker now (1.9 & above) through CLI can be specified volume plugin name, which docker daemon connects get the actual storage. The plugin has today reasonable hooks for maintaining and cleaning the storage. I was wondering if there is any analysis done on the support of this in the code? What I understand the slave code which calls in docker cli would need this additional parameter to be passed into. Thx
