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 "Shane Kumpf (JIRA)" <ji...@apache.org> on 2018/02/02 13:41:00 UTC
[jira] [Commented] (YARN-6456) Isolation of Docker containers In
LinuxContainerExecutor
[ https://issues.apache.org/jira/browse/YARN-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350340#comment-16350340 ]
Shane Kumpf commented on YARN-6456:
-----------------------------------
[~miklos.szegedi@cloudera.com] - I believe YARN-7815 will address #1 and YARN-7814 removes the automatic mounting for #2. Should we re-purpose this issue to focus on #3 and make it a subtask of YARN-3611? Thanks.
> Isolation of Docker containers In LinuxContainerExecutor
> --------------------------------------------------------
>
> Key: YARN-6456
> URL: https://issues.apache.org/jira/browse/YARN-6456
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Miklos Szegedi
> Priority: Major
>
> One reason to use Docker containers is to be able to isolate different workloads, even, if they run as the same user.
> I have noticed some issues in the current design:
> 1. DockerLinuxContainerRuntime mounts containerLocalDirs {{nm-local-dir/usercache/user/appcache/application_1491598755372_0011/}} and userLocalDirs {{nm-local-dir/usercache/user/}}, so that a container can see and modify the files of another container. I think the application file cache directory should be enough for the container to run in most of the cases.
> 2. The whole cgroups directory is mounted. Would the container directory be enough?
> 3. There is no way to enforce exclusive use of Docker for all containers. There should be an option that it is not the user but the admin that requires to use Docker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org