[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980159#comment-13980159
]
Abin Shahab commented on YARN-1964:
-----------------------------------
Wangda Tan, I like your suggestion. The patch that I've posted has a version of
the DefaultContainerExecutor that launches Docker. Right now the Executor type
and Container names can be changed only on yarn-site.xml. However, I would like
to move it down to the job configuration so that we can achieve what've said:
For matlab jobs, users would specify the matlab container in their jobconf, for
their regular mapred job, they would specify yarn containers.
Junping Du, I agree with the idea of a generic executor. The
LinuxContainerExecutor can be extended to launch docker. However, we have to
work out how the resource-isolation management is handled between docker and
CgroupsLCEResourcesHandler.
Thanks for the feedback!
> Support Docker containers 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
>
>
> 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)
