Thanks for the tip, I did actually notice the project when trying to find a solution for my problem. This project seems to be about leveraging external Docker volume drivers, which is certainly also interesting but I'm trying to use the build in Mesos persistent storage.
Actually I just noticed that I can mount the volumes that I created with Mesos it is just that when I specify a relative path for the container path in the volume the mount shows up below /mnt/mesos/sandbox and when I specify an absolute path it is being ignored as according to the Mesos log slashes are not allowed in the container path. So now problem is that I would like to have the mount at a different location. On 23/06/16 20:43, Vaibhav Khanduja wrote: > Hi Hendrik, > > If you want to run Docker jobs, it may be a good idea to get volumes > from “Docker” volume plugin. > > There is a project by EMC - mesos-dvdi, which abstracts the volume > creation. Please check this out and it should work with your scheduler … > > > https://github.com/emccode/mesos-module-dvdi > > Thx > > > > On Thu, Jun 23, 2016 at 7:56 AM, Hendrik Haddorp > <[email protected] <mailto:[email protected]>> wrote: > > Hi, > > I'm trying to write a Mesos framework that should create persistent > volumes and then start a Docker container that uses this. So far I was > able to dynamically reserve resources (cpu, memory and disk) and > create > a persistent volume in the reserved disk space. I'm also able to > launch > a Docker container. I just can't figure out how to connect these > correctly. I either get told that some fields are not set > correctly, end > up with mounting a path on the host system or nothing at all seems to > happen. > > Would be nice if somebody could show how a TaskInfo protobuf would > need > to get filled to achieve this. > > thanks, > Hendrik > >
