[MESOS-5102] Support persistent volumes via Docker volume drivers

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.28.0
• Component/s: containerization, docker
• External issue URL: https://github.com/mesosphere/marathon/issues/2493
• Assignee: Unassigned
• Reporter: Tobias Mueller
• Created: 04/Apr/16 07:08
• Updated: 07/Jun/16 16:29
• Resolved: 07/Jun/16 16:29

Description

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

Issue Links

• duplicates: MESOS-4355 Implement isolator for Docker volume
• is related to: MESOS-4355 Implement isolator for Docker volume