[
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
This patch simplifies the use-case by exposing only one docker configuration
param: The image. Now the user must configure the image completely so that all
require resources and environment variables are defined in the image.
> 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-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)
