[
https://issues.apache.org/jira/browse/MESOS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085911#comment-16085911
]
David Bosschaert commented on MESOS-6384:
-----------------------------------------
Hi [~cmaxson] - I am not aware of a real solution at this stage.
Basically the workaround is to always create the volume beforehand using some
other mechanism, i.e. direct calls into the cloud such as AWS or Azure and
create the cloud disk volume that way. This brings a timing problem though as
you need to make sure that the volume is definitely there before the container
is launched otherwise it'll create it on demand with the default as mentioned.
> Support for size with create-on-demand volumes with Docker containerizer
> ------------------------------------------------------------------------
>
> Key: MESOS-6384
> URL: https://issues.apache.org/jira/browse/MESOS-6384
> Project: Mesos
> Issue Type: Improvement
> Components: docker
> Reporter: David Bosschaert
>
> This issue was originally worded as marathon issue
> https://github.com/mesosphere/marathon/issues/4583
> When specifying an external volume to be used with a docker container, the
> size of the external volume cannot be specified. External volumes are often
> created on-demand, when first used, but if no size can be specified all
> volumes will have the same, default size.
> In the case if DVDI with REXRay, the default size is 16GB. This default can
> be modified but it is clearly desirable to be able to specify per-volume what
> the size should be.
> When mesos creates the external volume on-demand, which I presume normally
> happens before the docker container is launched, it should allow the
> specification of the size of this volume.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
