[ https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026170#comment-14026170 ]
Dinesh Subhraveti commented on YARN-1964: ----------------------------------------- We are putting together issues across YARN and Docker projects related to this work as a wiki page: https://wiki.apache.org/hadoop/dineshs/IsolatingYarnAppsInDockerContainers. If you happen to be at Dockercon tomorrow, join our Hadoop BoF session for more discussion! This blog post has some background as well: https://www.altiscale.com/making-docker-work-yarn/ > 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-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.2#6252)