[
https://issues.apache.org/jira/browse/AURORA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455953#comment-15455953
]
Zhitao Li commented on AURORA-1107:
-----------------------------------
We are evaluating use Mesos containerizer to replace the DockerContainerizer in
our Aurora cluster. One blocker I found is that current Aurora integration of
supporting Mesos containerizer does not expose the {{volumes}} in
{{ContainerInfo}}. With DockerContainerizer, we are bypassing this issue by
directly pass {{--volume}} argument to docker daemon.
Given this seems like the closest ticket, can we discuss how to expose this
option to each job?
> 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)
