[ https://issues.apache.org/jira/browse/MESOS-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225970#comment-15225970 ]
Tobias Mueller commented on MESOS-5102: --------------------------------------- Thanks again! Sorry for probably asking a blunt question, but what is the reason why you chose not tu use the "native" docker volume mechanisms (other than getting rid of the Docker dependency)? As far as I understood, Docker would transparently create a volume if it's not existing, or use an existing one. I'm a Mesos beginner, but I thought it would maybe be sufficient to pass the --volume-driver flag together with the -v volumeName:/containerMountpoint flag to handle Docker volume driver volumes when the agent starts the container via "docker run ...". If I understand correctly, with the current concept, it would not be possible to create a volume when launching a Marathon app, because the volume would have to be create upfront? Is there any integration for Marathon apps planned? If so, how? Sorry for all these questions, but I think (at least for us) it's important to understand how the persistent volumes will work, because we'll also need to run stateful serives on Mesos, and currently I don't really understand how this will work in the future. I guess this can really be a showstopper for a lot of use cases. > 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)