[ 
https://issues.apache.org/jira/browse/MESOS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Babineau updated MESOS-2374:
---------------------------------
    Description: 
There is no convenient way to mount directories within the sandbox as container 
volumes.

A common use case is injecting the contents of one or more fetched-URI 
archives, each of which needs to be extracted and mounted inside the container.

While it is possible to access sandbox subdirectories via $MESOS_SANDBOX, this 
presumes 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. Furthermore, the container must be 
aware of $MESOS_SANDBOX to be able to use the access these files at all.

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

  was:
There is no convenient way to mount directories within the sandbox as container 
volumes.

A common use case is injecting the contents of one or more fetched-URI 
archives, each of which needs to be extracted and mounted inside the container.

While it is possible to access sandbox subdirectories via $MESOS_SANDBOX, this 
presumes 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. Furthermore, the container must be 
aware of $MESOS_SANDBOX to be able to use the access these files at all.

One potential solution is to 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).


> 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 directories within the sandbox as 
> container volumes.
> A common use case is injecting the contents of one or more fetched-URI 
> archives, each of which needs to be extracted and mounted inside the 
> container.
> While it is possible to access sandbox subdirectories via $MESOS_SANDBOX, 
> this presumes 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. Furthermore, the container must be 
> aware of $MESOS_SANDBOX to be able to use the access these files at all.
> 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)

Reply via email to