[
https://issues.apache.org/jira/browse/AURORA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223269#comment-15223269
]
Stephan Erb edited comment on AURORA-1107 at 4/3/16 1:01 PM:
-------------------------------------------------------------
We have global container mounts. Does this fix this issue?
```
-global_container_mounts=[]
A comma seperated list of mount points (in host:container form) to mount
into all (non-mesos) containers.
(org.apache.aurora.scheduler.configuration.executor.ExecutorModule.global_container_mounts)
```
was (Author: stephanerb):
We have global container mounts. Does this fix this issue?
```
> Add support for mounting external volumes into docker containers
> ----------------------------------------------------------------
>
> Key: AURORA-1107
> URL: https://issues.apache.org/jira/browse/AURORA-1107
> Project: Aurora
> Issue Type: Task
> Components: Docker
> Reporter: Steve Niemitz
> Assignee: Steve Niemitz
> Priority: Minor
>
> The Mesos docker API allows specifying volumes on the host to mount into the
> container when it runs. We should expose this. I propose:
> - Add a volumes() set to the Docker object in base.py
> - Add a similar set to the DockerContainer struct in api.thrift
> - Create a way for administrators to restrict the ability to use this.
> Because mounts are set up by the docker daemon, they effectively allow
> someone who can configure mounts to access anything on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
