[
https://issues.apache.org/jira/browse/YARN-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238428#comment-16238428
]
Eric Yang commented on YARN-7430:
---------------------------------
Looks like we built too many knobs for this to occur. If
{{yarn.nodemanager.runtime.linux.enable-userremapping.allowed}} is set to
{{false}} and enabled privileged container, then privileges escalation will
occur unintentionally. If both flags are set to true, then privileges
escalation doesn't occur unintentionally. Therefore, we can fix this problem
by removing {{yarn.nodemanager.runtime.linux.enable-userremapping.allowed}}
flag and always enforce remapping.
> User and Group mapping are incorrect in docker container
> --------------------------------------------------------
>
> Key: YARN-7430
> URL: https://issues.apache.org/jira/browse/YARN-7430
> Project: Hadoop YARN
> Issue Type: Bug
> Components: security, yarn
> Affects Versions: 2.9.0, 3.0.0
> Reporter: Eric Yang
> Assignee: Varun Vasudev
> Priority: Blocker
>
> In YARN-4266, the recommendation was to use -u [uid]:[gid] numeric values to
> enforce user and group for the running user. In YARN-6623, this translated
> to --user=test --group-add=group1. The code no longer enforce group
> correctly for launched process.
> In addition, the implementation in YARN-6623 requires the user and group
> information to exist in container to translate username and group to uid/gid.
> For users on LDAP, there is no good way to populate container with user and
> group information.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
