[
https://issues.apache.org/jira/browse/YARN-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286462#comment-16286462
]
Vinod Kumar Vavilapalli commented on YARN-7516:
-----------------------------------------------
I very much like this proposal as a simple way to block untrusted images.
Minor comments
- By default, no images are trusted? From security perspective, this is good.
But if we go this way, we should add in site documentation as one of the
required settings.
- Rename the option to
{{yarn.nodemanager.runtime.linux.docker.trusted-registry}}?
- Add your three category examples in yarn-default.xml description of the
property and in site documentation?
- DockerLinuxContainerRuntime: Read the value of the config only once in the
object initialization?
- Testing
-- We are also allowing privileged containers also only from trusted
registry - this is good. Add an explicit test?
-- I may or may not be reading this correctly, but there doesn't seem to be
a negative test which shows that if an image is not trusted, we verify that
behavior.
> Security check for untrusted docker image
> -----------------------------------------
>
> Key: YARN-7516
> URL: https://issues.apache.org/jira/browse/YARN-7516
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Yang
> Assignee: Eric Yang
> Attachments: YARN-7516.001.patch
>
>
> Hadoop YARN Services can support using private docker registry image or
> docker image from docker hub. In current implementation, Hadoop security is
> enforced through username and group membership, and enforce uid:gid
> consistency in docker container and distributed file system. There is cloud
> use case for having ability to run untrusted docker image on the same cluster
> for testing.
> The basic requirement for untrusted container is to ensure all kernel and
> root privileges are dropped, and there is no interaction with distributed
> file system to avoid contamination. We can probably enforce detection of
> untrusted docker image by checking the following:
> # If docker image is from public docker hub repository, the container is
> automatically flagged as insecure, and disk volume mount are disabled
> automatically, and drop all kernel capabilities.
> # If docker image is from private repository in docker hub, and there is a
> white list to allow the private repository, disk volume mount is allowed,
> kernel capabilities follows the allowed list.
> # If docker image is from private trusted registry with image name like
> "private.registry.local:5000/centos", and white list allows this private
> trusted repository. Disk volume mount is allowed, kernel capabilities
> follows the allowed list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
