hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-7654) Support ENTRY_POINT for docker container
Date Wed, 28 Mar 2018 23:39:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418246#comment-16418246
] 

Eric Yang edited comment on YARN-7654 at 3/28/18 11:38 PM:
-----------------------------------------------------------

[~jlowe] The patch has been rebased to depend on YARN-7221 patch 12.  Base on our discussion
today, the new proposal is to create a section in cmd file, i.e.

{code}
[docker-command-execution]
  ...
[docker-command-environment]
  LANGUAGE=en_US.UTF-8
  YARN_CONTAINER_RUN_TIME_DOCKER_CONTAINER_HOSTNAME=appcatalog-0.abc.hbase.ycluster
  ..
{code}

This can avoid to get stuck by the pipe delimiter in environment variables.  Is this the proposed
approach?


was (Author: eyang):
[~jlowe] The patch has been rebased to depend on YARN-7221 patch 12.  Base on our discussion
today, the new proposal is to create a section in cmd file, i.e.

[docker-command-execution]
  ...
[docker-command-environment]
  LANGUAGE=en_US.UTF-8
  YARN_CONTAINER_RUN_TIME_DOCKER_CONTAINER_HOSTNAME=appcatalog-0.abc.hbase.ycluster
  ..

This can avoid to get stuck by the pipe delimiter in environment variables.  Is this the proposed
approach?

> Support ENTRY_POINT for docker container
> ----------------------------------------
>
>                 Key: YARN-7654
>                 URL: https://issues.apache.org/jira/browse/YARN-7654
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>    Affects Versions: 3.1.0
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Blocker
>         Attachments: YARN-7654.001.patch, YARN-7654.002.patch, YARN-7654.003.patch, YARN-7654.004.patch,
YARN-7654.005.patch, YARN-7654.006.patch
>
>
> Docker image may have ENTRY_POINT predefined, but this is not supported in the current
implementation.  It would be nice if we can detect existence of {{launch_command}} and base
on this variable launch docker container in different ways:
> h3. Launch command exists
> {code}
> docker run [image]:[version]
> docker exec [container_id] [launch_command]
> {code}
> h3. Use ENTRY_POINT
> {code}
> docker run [image]:[version]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message