[jira] [Updated] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor
[
https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-3853:
--
Labels: Docker (was: )
> 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
>Priority: Major
> Labels: Docker
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: YARN-3853.001.patch, YARN-3853.002.patch
>
>
> Create a new DockerContainerRuntime that implements support for docker
> containers via container-executor. LinuxContainerExecutor should default to
> current behavior when launching containers but switch to docker when
> requested.
> Overview
> ===
> The current mechanism of launching/signaling containers is moved to its own
> (default) container runtime. In order to use docker container runtime a
> couple of environment variables have to be set. This will have to be
> revisited when we have a first class client side API to specify different
> container types and associated parameters. Using ‘pi’ as an example and using
> a custom docker image, this is how you could use the docker container runtime
> (LinuxContainerExecutor must be in use and the docker daemon needs to be
> running) :
> {code}
> export
> YARN_EXAMPLES_JAR=./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar
> bin/yarn jar $YARN_EXAMPLES_JAR pi
> -Dmapreduce.map.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dyarn.app.mapreduce.am.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dmapreduce.reduce.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
> 4 1000
> {code}
>
> LinuxContainerExecutor can delegate to either runtime on a per container
> basis. If the docker container type is selected, LinuxContainerExecutor
> delegates to the DockerContainerRuntime which in turn uses docker support in
> the container-executor binary to launch/manage docker containers ( see
> YARN-3852 ) .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor
[
https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharta Seethana updated YARN-3853:
Attachment: YARN-3853.002.patch
Uploading a new version of the patch based on code review feedback.
> 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
> containers via container-executor. LinuxContainerExecutor should default to
> current behavior when launching containers but switch to docker when
> requested.
> Overview
> ===
> The current mechanism of launching/signaling containers is moved to its own
> (default) container runtime. In order to use docker container runtime a
> couple of environment variables have to be set. This will have to be
> revisited when we have a first class client side API to specify different
> container types and associated parameters. Using ‘pi’ as an example and using
> a custom docker image, this is how you could use the docker container runtime
> (LinuxContainerExecutor must be in use and the docker daemon needs to be
> running) :
> {code}
> export
> YARN_EXAMPLES_JAR=./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar
> bin/yarn jar $YARN_EXAMPLES_JAR pi
> -Dmapreduce.map.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dyarn.app.mapreduce.am.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dmapreduce.reduce.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
> 4 1000
> {code}
>
> LinuxContainerExecutor can delegate to either runtime on a per container
> basis. If the docker container type is selected, LinuxContainerExecutor
> delegates to the DockerContainerRuntime which in turn uses docker support in
> the container-executor binary to launch/manage docker containers ( see
> YARN-3852 ) .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor
[
https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidharta Seethana updated YARN-3853:
Description:
Create a new DockerContainerRuntime that implements support for docker
containers via container-executor. LinuxContainerExecutor should default to
current behavior when launching containers but switch to docker when requested.
Overview
===
The current mechanism of launching/signaling containers is moved to its own
(default) container runtime. In order to use docker container runtime a couple
of environment variables have to be set. This will have to be revisited when we
have a first class client side API to specify different container types and
associated parameters. Using ‘pi’ as an example and using a custom docker
image, this is how you could use the docker container runtime
(LinuxContainerExecutor must be in use and the docker daemon needs to be
running) :
{code}
export
YARN_EXAMPLES_JAR=./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar
bin/yarn jar $YARN_EXAMPLES_JAR pi
-Dmapreduce.map.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
-Dyarn.app.mapreduce.am.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
-Dmapreduce.reduce.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
4 1000
{code}
LinuxContainerExecutor can delegate to either runtime on a per container basis.
If the docker container type is selected, LinuxContainerExecutor delegates to
the DockerContainerRuntime which in turn uses docker support in the
container-executor binary to launch/manage docker containers ( see YARN-3852 )
.
was:Create a new DockerContainerRuntime that implements support for docker
containers via container-executor. LinuxContainerExecutor should default to
current behavior when launching containers but switch to docker when requested.
Till a first class ‘container type’ mechanism/API is available on the client
side, we could potentially implement this via environment variables.
> 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
>
>
> Create a new DockerContainerRuntime that implements support for docker
> containers via container-executor. LinuxContainerExecutor should default to
> current behavior when launching containers but switch to docker when
> requested.
> Overview
> ===
> The current mechanism of launching/signaling containers is moved to its own
> (default) container runtime. In order to use docker container runtime a
> couple of environment variables have to be set. This will have to be
> revisited when we have a first class client side API to specify different
> container types and associated parameters. Using ‘pi’ as an example and using
> a custom docker image, this is how you could use the docker container runtime
> (LinuxContainerExecutor must be in use and the docker daemon needs to be
> running) :
> {code}
> export
> YARN_EXAMPLES_JAR=./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar
> bin/yarn jar $YARN_EXAMPLES_JAR pi
> -Dmapreduce.map.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dyarn.app.mapreduce.am.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dmapreduce.reduce.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
> 4 1000
> {code}
>
> LinuxContainerExecutor can delegate to either runtime on a per container
> basis. If the docker container type is selected, LinuxContainerExecutor
> delegates to the DockerContainerRuntime which in turn uses docker support in
> the container-executor binary to launch/manage docker containers ( see
> YARN-3852 ) .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3853) Add docker container runtime support to LinuxContainterExecutor
[ https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3853: Attachment: YARN-3853.001.patch Attaching a patch - I apologize for the size of the patch - given how the runtime mechanism used currently, it isn't trivial to split this patch up. Please note that the patch here depends on changes from YARN-3853 . > 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 > > > Create a new DockerContainerRuntime that implements support for docker > containers via container-executor. LinuxContainerExecutor should default to > current behavior when launching containers but switch to docker when > requested. Till a first class ‘container type’ mechanism/API is available on > the client side, we could potentially implement this via environment > variables. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
