[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977923#comment-13977923
]
Junping Du commented on YARN-1964:
----------------------------------
+1 on specifying container type by app at runtime. Different container types
(default, LXC, docker, VM box, etc.) have different semantics on isolation of
security, namespace/env, performance, etc. Allowing app to specifying
technology of containers can largely broaden YARN's capability to meet
heterogenous app's requirement on isolation at the same time. In
implementation, I think current ContainerExecutor is already pluggable, but we
may not want to have several ContainerExecutor instances running inside of NMs.
May be we should only have a generic one (like: command pattern) to consolidate
operation details? Anyway, these discussions looks a little diverge from
original JIRA topic, may be we should file a separated JIRA to discuss this?
> Support Docker containers in YARN
> ---------------------------------
>
> Key: YARN-1964
> URL: https://issues.apache.org/jira/browse/YARN-1964
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Arun C Murthy
> Assignee: Abin Shahab
>
> 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)
