[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980238#comment-13980238
]
Wangda Tan commented on YARN-1964:
----------------------------------
[~ashahab], Thanks for you patch! As you said,
bq. However, I would like to move it down to the job configuration so that ...
I hope you could share more ideas job configuration you mentioned, is it a YARN
application specific configuration or it will be a part of NM's configuration?
I asked this because currently, we don't have such ability (Please correct me
if I was wrong) to specify application-specific config when running a YARN
application. We should leave an option to user specify their own configuration
to RM or NM, which can help them creating runtime-selectable modules (like
select CE at runtime).
> 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)
