You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2016/04/04 20:35:25 UTC

[jira] [Commented] (YARN-4595) Add support for configurable read-only mounts

    [ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224761#comment-15224761 ] 

Billie Rinaldi commented on YARN-4595:
--------------------------------------

bq. If we just restrict ourselves to accessing distributed-cache files inside a docker container

I agree, only mounting files from the distributed cache would be sufficient to support my use case and this would resolve the permissions issues that would be introduced if we allowed files to be mounted from other locations.

> Add support for configurable read-only mounts
> ---------------------------------------------
>
>                 Key: YARN-4595
>                 URL: https://issues.apache.org/jira/browse/YARN-4595
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>         Attachments: YARN-4595.1.patch, YARN-4595.2.patch
>
>
> Mounting files or directories from the host is one way of passing configuration and other information into a docker container.  We could allow the user to set a list of mounts in the environment of ContainerLaunchContext (e.g. /dir1:/targetdir1,/dir2:/targetdir2).  These would be mounted read-only to the specified target locations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)