[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980476#comment-13980476
]
Junping Du commented on YARN-1964:
----------------------------------
bq. I'd suggest this JIRA be renamed: Is it specifically to create a
DockerLinuxContainer ? Or is it broader. After all... Docker itself is a
"container" and YARN itself is a container, and YARN can run inside of docker,
and Multiple NM's can be launched as docker processes, and so on... so I think
the exact task of this JIRA should be clarified.
Agree with [~ashahab] that we should make this JIRA's scope focus on Docker
implementation. For more broader topics on supporting heterogenous containers
in runtime, [~leftnoteasy], [~jayunit100], how about we go further discussion
in a separated JIRA? - I just filed YARN-1983 for that.
> Create Docker analog of the LinuxContainerExecutor in YARN
> ----------------------------------------------------------
>
> Key: YARN-1964
> URL: https://issues.apache.org/jira/browse/YARN-1964
> Project: Hadoop YARN
> Issue Type: New Feature
> Affects Versions: 2.2.0
> Reporter: Arun C Murthy
> Assignee: Abin Shahab
> Attachments: yarn-1964-branch-2.2.0-docker.patch,
> yarn-1964-docker.patch
>
>
> Docker (https://www.docker.io/) is, increasingly, a very popular container
> technology.
> In context of YARN, the support for Docker will provide a very elegant
> solution to allow applications to *package* their software into a Docker
> container (entire Linux file system incl. custom versions of perl, python
> etc.) and use it as a blueprint to launch all their YARN containers with
> requisite software environment. This provides both consistency (all YARN
> containers will have the same software environment) and isolation (no
> interference with whatever is installed on the physical machine).
--
This message was sent by Atlassian JIRA
(v6.2#6252)