[jira] [Updated] (YARN-1964) Create Docker analog of the LinuxContainerExecutor in YARN

["Abin Shahab (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abin Shahab updated YARN-1964:
------------------------------
    Attachment: YARN-1964.patch

[~chenchun] Thanks a lot for your feedback.
I have made some of the changes you’ve requested.
1) I am excluding this if you look at writeLaunchEnv
2) In this first phase, we want to make this patch as simple as possible, and so we don’t want to add the burden of additional networking on the admin, which is why we are not changing this.
3) Similarly, we do not want to allow an unlimited number of configuration options to the docker container. We want to do this in future. Feel free to create a new task under the umbrella jira, and submit your pull request.
4) I have found it useful for certain jobs. Please look at my test.
5) Agreed, and changed.

[~ravihoo], I have made most of the changes you’ve requested. Let me know if anything else is needed.


> 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.patch, YARN-1964.patch, YARN-1964.patch, YARN-1964.patch, YARN-1964.patch, YARN-1964.patch, YARN-1964.patch, YARN-1964.patch, yarn-1964-branch-2.2.0-docker.patch, yarn-1964-branch-2.2.0-docker.patch, yarn-1964-docker.patch, yarn-1964-docker.patch, yarn-1964-docker.patch, yarn-1964-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.3.4#6332)