[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975937#comment-13975937
]
jay vyas commented on YARN-1964:
--------------------------------
Ah, sorry, i thought this was meant to be done at a different part of the stack
... So is this jira is specificaly to create a "DockerContainerExectuor" class?
then that would a really good idea, and I'm pretty sure it would be feasible.
I guess you'd need to add a few parameters to the core-site
in core-site.xml
{noformat}
<name>yarn.nodemanager.container-executor.class</name>
<value>DockerContainerExecutor</value>
{noformat}
and then maybe have a docker-site.xml
{noformat}
<name>docker.container.container.impl</name>
<value>PythonCentOSContainer</value>
<!-- then developers define their different container implementations below -->
<name>docker.container.container1</name>
<value>PythonCentOSContainer</value>
<name>docker.container.container2</name>
<value>MyContainerWithPostgres</value>
...
{noformat}
And then somehow localize resources in a docker-ish sort of way so that the
containers can see all the task resources properly.... Is that the idea here?
> 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: Arun C Murthy
>
> 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)
