[MESOS-2374] Support relative host paths for container volumes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.21.1
• Fix Version/s: 0.23.0
• Component/s: containerization, docker
• Labels: mesosphere
• Assignee: Timothy Chen
• Reporter: Mike Babineau
• Shepherd: Timothy Chen
• Created: 19/Feb/15 00:41
• Updated: 26/Nov/18 12:22
• Resolved: 26/Nov/18 12:22

Description

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