[ https://issues.apache.org/jira/browse/MESOS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597979#comment-14597979 ]
Ian Downes commented on MESOS-2374: ----------------------------------- In the MesosContainerizer a relative host_path in a volume is interpreted as relative to the work_dir, e.g., {container_path=/tmp, host_path=tmp, mode=RW} will create the directory $work_dir/tmp and mount it writeable at /tmp inside the container. This has uses both with and without filesystem containerization. > Support relative host paths for container volumes > ------------------------------------------------- > > Key: MESOS-2374 > URL: https://issues.apache.org/jira/browse/MESOS-2374 > Project: Mesos > Issue Type: Improvement > Components: containerization, docker > Affects Versions: 0.21.1 > Reporter: Mike Babineau > > There is no convenient way to mount sandbox subdirectories (such as unpacked > archives from fetched URIs) as container volumes. > While it is possible to access sandbox subdirectories via $MESOS_SANDBOX, > this presumes the container is expecting $MESOS_SANDBOX to be passed in. > Furthermore, it also expects the container already knows the resulting > subdirectory paths. Unfortunately, since the archives are extracted by the > fetcher, operators can not control these paths. Path changes to the extracted > archive must be accompanied by a container image change. > One potential solution: > Add support for relative paths to the containerizer. If the containerizer is > given a relative host path, it simply prepends the sandbox path before > passing it to Docker (or similar). -- This message was sent by Atlassian JIRA (v6.3.4#6332)