You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Tobias Mueller (JIRA)" <ji...@apache.org> on 2016/04/04 09:08:25 UTC

[jira] [Created] (MESOS-5102) Support persistent volumes via Docker volume drivers

Tobias Mueller created MESOS-5102:
-------------------------------------

             Summary: 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)