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 "Daniel Templeton (JIRA)" <ji...@apache.org> on 2016/09/22 17:41:20 UTC
[jira] [Comment Edited] (YARN-4266) Allow whitelisted users to
disable user re-mapping/squashing when launching docker containers
[ https://issues.apache.org/jira/browse/YARN-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513926#comment-15513926 ]
Daniel Templeton edited comment on YARN-4266 at 9/22/16 5:40 PM:
-----------------------------------------------------------------
After some discussion and thought, I think that 3.2 is OK as long as the user has the option to turn it off. In other words, the contract is that either the user takes care of making sure the container has the required user, or let YARN do it for you.
It might be worth exploring how far dockers logs could take us in dealing with the logging end of the problem.
Any comments, [~sidharta-s], [~vvasudev], or [~shanekumpf@gmail.com]?
was (Author: templedf):
After some discussion and thought, I think that 3.2 is OK as long as the user has the option to turn it off. In other words, the contract is that either the user takes care of making sure the container has the required user, or let YARN do it for you.
It might be worth exploring how far dockers logs could take us in dealing with the logging end of the problem.
> Allow whitelisted users to disable user re-mapping/squashing when launching docker containers
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-4266
> URL: https://issues.apache.org/jira/browse/YARN-4266
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Sidharta Seethana
> Assignee: Zhankun Tang
> Attachments: YARN-4266_Allow_whitelisted_users_to_disable_user_re-mapping.pdf, YARN-4266_Allow_whitelisted_users_to_disable_user_re-mapping_v2.pdf
>
>
> Docker provides a mechanism (the --user switch) that enables us to specify the user the container processes should run as. We use this mechanism today when launching docker containers . In non-secure mode, we run the docker container based on `yarn.nodemanager.linux-container-executor.nonsecure-mode.local-user` and in secure mode, as the submitting user. However, this mechanism breaks down with a large number of 'pre-created' images which don't necessarily have the users available within the image. Examples of such images include shared images that need to be used by multiple users. We need a way in which we can allow a pre-defined set of users to run containers based on existing images, without using the --user switch. There are some implications of disabling this user squashing that we'll need to work through : log aggregation, artifact deletion etc.,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org