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

Shane Kumpf commented on YARN-5534:
-----------------------------------

>From a usability stand point, I have to agree with 
>[[email protected]], expecting admins to define the white list in 
>two places is not ideal. If the two configs get out of sync, it will lead to 
>surprising behavior. While I'm not a fan of the current direction of moving 
>more and more functionality into container-executor, it seems there is no way 
>around doing so with the current design. I will need to move all of the 
>whitelist validation into container-executor to keep it in a single place. One 
>pitfall of this approach is that we can no longer fail fast and must spawn the 
>container-executor process before the validation occurs. If this is the 
>consensus on how we need to handle the whitelist, I will start to rework the 
>patch to move the configuration to container-executor.cfg and do all of 
>whitelist validation in container-executor.

> Allow whitelisted volume mounts 
> --------------------------------
>
>                 Key: YARN-5534
>                 URL: https://issues.apache.org/jira/browse/YARN-5534
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>            Reporter: luhuichun
>            Assignee: Shane Kumpf
>         Attachments: YARN-5534.001.patch, YARN-5534.002.patch, 
> YARN-5534.003.patch
>
>
> Introduction 
> 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 has 
> been resolved in YARN-4595
> 2.Problem Definition
> Bug mounting arbitrary volumes into a Docker container can be a security risk.
> 3.Possible solutions
> one approach to provide safe mounts is to allow the cluster administrator to 
> configure a set of parent directories as white list mounting directories.
>  Add a property named yarn.nodemanager.volume-mounts.white-list, when 
> container executor do mount checking, only the allowed directories or 
> sub-directories can be mounted. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to