Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 15 Jun 2016 00:34:30 +0000 (UTC)
From: "Sidharta Seethana (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12828536.1431131193000.3746.1465950870489@Atlassian.JIRA>
In-Reply-To: <JIRA.12828536.1431131193000@Atlassian.JIRA>
References: <JIRA.12828536.1431131193000@Atlassian.JIRA> <JIRA.12828536.1431131193184@arcas>
Subject: [jira] [Commented] (YARN-3611) Support Docker Containers In
 LinuxContainerExecutor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 15 Jun 2016 00:34:32 -0000


    [ https://issues.apache.org/jira/browse/YARN-3611?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15330=
932#comment-15330932 ]=20

Sidharta Seethana commented on YARN-3611:
-----------------------------------------

hi [~templedf], please go ahead and file a JIRA for adding docs. Thanks!

> Support Docker Containers In LinuxContainerExecutor
> ---------------------------------------------------
>
>                 Key: YARN-3611
>                 URL: https://issues.apache.org/jira/browse/YARN-3611
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Sidharta Seethana
>            Assignee: Sidharta Seethana
>
> Support Docker Containers In LinuxContainerExecutor
> LinuxContainerExecutor provides useful functionality today with respect t=
o localization, cgroups based resource management and isolation for CPU, ne=
twork, disk etc. as well as security with a well-defined mechanism to execu=
te privileged operations using the container-executor utility.  Bringing do=
cker support to LinuxContainerExecutor lets us use all of this functionalit=
y when running docker containers under YARN, while not requiring users and =
admins to configure and use a different ContainerExecutor.=20
> There are several aspects here that need to be worked through :
> * Mechanism(s) to let clients request docker-specific functionality - we =
could initially implement this via environment variables without impacting =
the client API.
> * Security - both docker daemon as well as application
> * Docker image localization
> * Running a docker container via container-executor as a specified user
> * =E2=80=9CIsolate=E2=80=9D the docker container in terms of CPU/network/=
disk/etc
> * Communicating with and/or signaling the running container (ensure corre=
ct pid handling)
> * Figure out workarounds for certain performance-sensitive scenarios like=
 HDFS short-circuit reads=20
> * All of these need to be achieved without changing the current behavior =
of LinuxContainerExecutor


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org