hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-7221) Add security check for privileged docker container
Date Mon, 26 Feb 2018 23:58:00 GMT

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

Eric Yang edited comment on YARN-7221 at 2/26/18 11:57 PM:
-----------------------------------------------------------

YARN-7654 will change the launcher script invocation to be external of docker container instead
of running launcher script inside docker container.  Until that work is completed, it is not
safe to run privileged container because data written to yarn localizer directory might contain
root user files.  This will prevent localized directory from clean up.  YARN-7654 might not
be completed in 3.1 release.  Hence, removing this JIRA as blocker for 3.1 release.


was (Author: eyang):
YARN-7654 will change the launcher script invocation to be external of docker container instead
of running launcher script inside docker container.  Until that work is completed, it is not
safe to run privileged container because data written to yarn localizer directory might contain
root user files.  This will prevent localized directory from clean up.  YARN-7654 might not
be completed in 3.1 release.  Hence, removing this JIAR as blocker for 3.1 release.

> Add security check for privileged docker container
> --------------------------------------------------
>
>                 Key: YARN-7221
>                 URL: https://issues.apache.org/jira/browse/YARN-7221
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 3.0.0, 3.1.0
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Major
>         Attachments: YARN-7221.001.patch, YARN-7221.002.patch, YARN-7221.003.patch, YARN-7221.004.patch,
YARN-7221.005.patch
>
>
> When a docker is running with privileges, majority of the use case is to have some program
running with root then drop privileges to another user.  i.e. httpd to start with privileged
and bind to port 80, then drop privileges to www user.  
> # We should add security check for submitting users, to verify they have "sudo" access
to run privileged container.  
> # We should remove --user=uid:gid for privileged containers.  
>  
> Docker can be launched with --privileged=true, and --user=uid:gid flag.  With this parameter
combinations, user will not have access to become root user.  All docker exec command will
be drop to uid:gid user to run instead of granting privileges.  User can gain root privileges
if container file system contains files that give user extra power, but this type of image
is considered as dangerous.  Non-privileged user can launch container with special bits to
acquire same level of root power.  Hence, we lose control of which image should be run with
--privileges, and who have sudo rights to use privileged container images.  As the result,
we should check for sudo access then decide to parameterize --privileged=true OR --user=uid:gid.
 This will avoid leading developer down the wrong path.



--
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


Mime
View raw message