[ https://issues.apache.org/jira/browse/MESOS-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226120#comment-15226120 ]
Guangya Liu commented on MESOS-5102: ------------------------------------ For 1), yes, you are right. We will remove the dependency once the dvdcli was reimplemented by C++. For 2), please take a look at the following code as an example: {code} TaskInfo task; .... ContainerInfo containerInfo; Volume* volume1 = containerInfo.add_volumes(); volume1->set_container_path("/tmp/abc1"); volume1->mutable_source()->set_type(Volume::Source::DOCKER_VOLUME); volume1->mutable_source()->mutable_docker_volume()->set_driver("convoy"); volume1->mutable_source()->mutable_docker_volume()->set_name("nfs-vol1"); Volume* volume2 = containerInfo.add_volumes(); volume2->set_container_path("/tmp/abc2"); volume2->mutable_source()->set_type(Volume::Source::DOCKER_VOLUME); volume2->mutable_source()->mutable_docker_volume()->set_driver("convoy"); volume2->mutable_source()->mutable_docker_volume()->set_name("nfs-vol2"); volume2->mutable_source()->mutable_docker_volume()->add_driver_options("iops=150"); task.mutable_container()->CopyFrom(containerInfo); {code} > Support persistent volumes via Docker volume drivers > ---------------------------------------------------- > > Key: MESOS-5102 > URL: https://issues.apache.org/jira/browse/MESOS-5102 > Project: Mesos > Issue Type: Improvement > Components: containerization, docker > Affects Versions: 0.28.0 > Reporter: Tobias Mueller > > To my understanding it's currently not possible to create persistent volumes > via Docker volume drivers/plugins. This limits IMHO the usability of the > persistent volumes to a large extend if people are using distributed > filesystems like GlusterFS or Ceph. > There was a discussion in a GitHub issue > (https://github.com/mesosphere/marathon/issues/2493#issuecomment-196743212) > about this, leading to the conclusion that it's currently not possible to use > Docker volume drivers. > Looking at http://mesos.apache.org/documentation/latest/persistent-volume/ I > guess it would make sense to add a property for the Docker volume driver in > the Offer::Operation::CREATE operation so that the --volume-driver flag can > be added when the Docker containers are launched, e.g. via Marathon. > References: > * https://docs.docker.com/engine/extend/plugins_volume/ > StackOverflow questions: > * > http://stackoverflow.com/questions/36361483/example-marathon-json-deployment-file-when-using-glusterfs-volume-driver/36396205 > * > http://stackoverflow.com/questions/36242383/mesos-slaves-reject-all-marathon-jobs-with-persistent-volumes-claims-no-space-a -- This message was sent by Atlassian JIRA (v6.3.4#6332)