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 ABE9918030 for ; Fri, 24 Jul 2015 18:07:08 +0000 (UTC) Received: (qmail 8938 invoked by uid 500); 24 Jul 2015 18:07:08 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 8899 invoked by uid 500); 24 Jul 2015 18:07:08 -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 8888 invoked by uid 99); 24 Jul 2015 18:07:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2015 18:07:08 +0000 Date: Fri, 24 Jul 2015 18:07:08 +0000 (UTC) From: "Varun Vasudev (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor 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-3853?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14640= 838#comment-14640838 ]=20 Varun Vasudev commented on YARN-3853: ------------------------------------- +1. I'll commit this on Monday if no one objects. One question - can you pl= ease clarify why we're using "net=3Dhost"? Thanks! > Add docker container runtime support to LinuxContainterExecutor > --------------------------------------------------------------- > > Key: YARN-3853 > URL: https://issues.apache.org/jira/browse/YARN-3853 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn > Reporter: Sidharta Seethana > Assignee: Sidharta Seethana > Attachments: YARN-3853.001.patch, YARN-3853.002.patch > > > Create a new DockerContainerRuntime that implements support for docker co= ntainers via container-executor. LinuxContainerExecutor should default to c= urrent behavior when launching containers but switch to docker when request= ed.=20 > Overview > =3D=3D=3D > The current mechanism of launching/signaling containers is moved to its o= wn (default) container runtime. In order to use docker container runtime a = couple of environment variables have to be set. This will have to be revisi= ted when we have a first class client side API to specify different contain= er types and associated parameters. Using =E2=80=98pi=E2=80=99 as an exampl= e and using a custom docker image, this is how you could use the docker con= tainer runtime (LinuxContainerExecutor must be in use and the docker daemon= needs to be running) : > {code} > export YARN_EXAMPLES_JAR=3D./share/hadoop/mapreduce/hadoop-mapreduce-exam= ples-*.jar > bin/yarn jar $YARN_EXAMPLES_JAR pi -Dmapreduce.map.env=3D"YARN_CONTAINER_= RUNTIME_TYPE=3Ddocker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=3Dashahab/hadoop-= trunk" -Dyarn.app.mapreduce.am.env=3D"YARN_CONTAINER_RUNTIME_TYPE=3Ddocker,= YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=3Dashahab/hadoop-trunk" -Dmapreduce.re= duce.env=3D"YARN_CONTAINER_RUNTIME_TYPE=3Ddocker,YARN_CONTAINER_RUNTIME_DOC= KER_IMAGE=3Dashahab/hadoop-trunk" 4 1000 > {code} > =20 > LinuxContainerExecutor can delegate to either runtime on a per container = basis. If the docker container type is selected, LinuxContainerExecutor del= egates to the DockerContainerRuntime which in turn uses docker support in t= he container-executor binary to launch/manage docker containers ( see YARN-= 3852 ) .=20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)