You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2016/05/16 20:37:13 UTC

[jira] [Commented] (MESOS-5389) docker containerizer should prefix relative volume.container_path values with the path to the sandbox

    [ https://issues.apache.org/jira/browse/MESOS-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285245#comment-15285245 ] 

Gilbert Song commented on MESOS-5389:
-------------------------------------

Thanks [~jdef], it should not be hard to do that, but a discussion may be needed about whether or not we want to do that. Because that's totally different from docker user's behavior. Only absolute path is allowed in docker daemon when they do `docker run -v ....`.

I understand that you want to make two containerizer consistent in behavior, but this issue belongs to the diff semantic for these two containerizes, and we do have similar difference on supporting docker runtime on these two containerizes. This difference also comes from the mesos containerizer support with/without image rootfs, but docker containerizer only use docker daemon.

Definitely we need more discussion. To me, I would prefer keep the current semantic. And if users want to use the docker containerizer with relative path, they can just specify the container_path to the sandbox (e.g., /mnt/mesos/sandbox/tmp).

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