[
https://issues.apache.org/jira/browse/YARN-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958364#comment-14958364
]
Sidharta Seethana commented on YARN-4262:
-----------------------------------------
bq, should we expose such functionality to anybody who is not in the 'admin'
role for the cluster?
What I meant here is : if users A, B, C are admins in a cluster, should *any*
users apart from A, B, C be allowed to run privileged containers? In other
words, should the list for docker privileged mode be entirely
orthogonal/unrelated to the admin list or should it be a subset? If I
understand you correctly, you are suggesting that the list should be completely
unrelated to the admin role. I see the value in separation of privileges but I
thought tying this to the admin role might lead to this feature being used more
carefully - hence the path chosen in the first version of the patch.
I'll upload a new patch using a different list as you suggested. I'll update
the description accordingly.
> Allow admins to run privileged docker containers.
> --------------------------------------------------
>
> Key: YARN-4262
> URL: https://issues.apache.org/jira/browse/YARN-4262
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Sidharta Seethana
> Assignee: Sidharta Seethana
> Attachments: YARN-4262.001.patch
>
>
> There are scenarios where privileged containers are necessary in order to run
> certain kinds of applications (one example is trying to run postresql/oracle
> inside containers). However, given the security implications, we should
> ensure that :
> 1) privileged containers are disabled by default, even for admins
> 2) if enabled, only admins should be allowed to launch such containers and
> 3) Not all containers launched by admin users need to be privileged
> containers : admin users need to explicitly request that a privileged
> container be launched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
