[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977893#comment-13977893
]
Wangda Tan commented on YARN-1964:
----------------------------------
It's really a great feature to make users can run/distribute packages to YARN
platform quite simple.
I'm wondering if it good to add a pluggable ContainerExecutor which can be
specified by application at *runtime*. Which means, app#1 can choose
LinuxContainerExecutor, app#2 can choose DockerContainerExecutor, etc.
Different container executors will do resource isolation/enforcement
separately. But they will have similar behavior to the upper layer module (like
ContainerLauncher, ContainersMonitor, etc.). Because users have to pack
everything to Docker package if we don't have such mechanism.
Hope to get your thoughts for on 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)
