Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 267F510235 for ; Thu, 22 Jan 2015 18:36:38 +0000 (UTC) Received: (qmail 63003 invoked by uid 500); 22 Jan 2015 18:36:38 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 62957 invoked by uid 500); 22 Jan 2015 18:36:38 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 62943 invoked by uid 99); 22 Jan 2015 18:36:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2015 18:36:38 +0000 Date: Thu, 22 Jan 2015 18:36:37 +0000 (UTC) From: "Chen He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2466) Umbrella issue for Yarn launched Docker Containers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-2466?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14287= 941#comment-14287941 ]=20 Chen He commented on YARN-2466: ------------------------------- Hi [~ashahab], if you don't mind, I will create a sub-task JIRA to trace th= is issue.=20 > Umbrella issue for Yarn launched Docker Containers > -------------------------------------------------- > > Key: YARN-2466 > URL: https://issues.apache.org/jira/browse/YARN-2466 > Project: Hadoop YARN > Issue Type: New Feature > Affects Versions: 2.4.1 > Reporter: Abin Shahab > Assignee: Abin Shahab > > Docker (https://www.docker.io/) is, increasingly, a very popular containe= r technology. > In context of YARN, the support for Docker will provide a very elegant so= lution to allow applications to package their software into a Docker contai= ner (entire Linux file system incl. custom versions of perl, python etc.) a= nd 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 wit= h whatever is installed on the physical machine). > In addition to software isolation mentioned above, Docker containers will= provide resource, network, and user-namespace isolation.=20 > Docker provides resource isolation through cgroups, similar to LinuxConta= inerExecutor. This prevents one job from taking other jobs resource(memory = and CPU) on the same hadoop cluster.=20 > User-namespace isolation will ensure that the root on the container is ma= pped an unprivileged user on the host. This is currently being added to Doc= ker. > Network isolation will ensure that one user=E2=80=99s network traffic is = completely isolated from another user=E2=80=99s network traffic.=20 > Last but not the least, the interaction of Docker and Kerberos will have = to be worked out. These Docker containers must work in a secure hadoop envi= ronment. > Additional details are here: https://wiki.apache.org/hadoop/dineshs/Isola= tingYarnAppsInDockerContainers -- This message was sent by Atlassian JIRA (v6.3.4#6332)