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

Eric Yang commented on YARN-7654:
---------------------------------

[~Jim_Brennan] [~ebadger] The answers are not straight forward, and here are 
the possible scenarios:

1.  Dockerfile describes ENV variables, they are the default value if user do 
not override them.
2.  User can pass in -e K=V to override the the default values.
3.  For hardcoded values, they can be described in /etc/profile or 
/root/.bashrc file, if the first process is bash.

This means docker will mostly inherit values from image, then follow by YARN 
enforced values for images that utilize ENTRY_POINT.  Do you see any hole that 
might lead to undesired behavior?

> 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to