[
https://issues.apache.org/jira/browse/MESOS-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286383#comment-15286383
]
James DeFelice commented on MESOS-5389:
---------------------------------------
Disagree. The containerizers should both being able to accept relative
containerPath's otherwise the API's become confusing for the end user. The
user doesn't always know the path to the sandbox that Mesos (or dc/os) will
append so asking the user to specify an absolute containerPath (if they
want the vol mounted in their sandbox) is a non-starter.
--
James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)
> docker containerizer should prefix relative volume.container_path values with
> the path to the sandbox
> -----------------------------------------------------------------------------------------------------
>
> Key: MESOS-5389
> URL: https://issues.apache.org/jira/browse/MESOS-5389
> Project: Mesos
> Issue Type: Bug
> Reporter: James DeFelice
> Labels: docker, mesosphere, storage, volumes
>
> docker containerizer currently requires absolute paths for values of
> volume.container_path. this is inconsistent with the mesos containerizer
> which requires relative container_path. it makes for a confusing API. both at
> the Mesos level as well as at the Marathon level.
> ideally the docker containerizer would allow a framework to specify a
> relative path for volume.container_path and in such cases automatically
> convert it to an absolute path by prepending the sandbox directory to it.
> /cc [~jieyu]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
