hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4595) Add support for configurable read-only mounts
Date Thu, 28 Apr 2016 17:10:13 GMT

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

Billie Rinaldi commented on YARN-4595:

[~aw], I tested mounting symlinks into docker containers and found that you were correct in
the case of mounting a symlink directly (-v symlink:dest).  My new patch checks to make sure
the mount is not a symlink so that this will not happen.  In the case where a directory containing
a symlink is mounted into a container, the target of the symlink will not be accessible in
the container (unless the target exists in the container).  I believe this new patch addresses
your concerns.

> 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, YARN-4595.3.patch, YARN-4595.4.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.
> Due to permissions and user concerns, for this ticket we will require the mounts to be
resources that are in the distributed cache.

This message was sent by Atlassian JIRA

View raw message