Eric Badger commented on YARN-7654:

bq. I plan to retain the current behavior. If USE_ENTRY_POINT is enabled, then 
it follows the second method for environment construction, and user defined 
environment variable may override image supplied environment. This depends on 
how the image is arranged.
But how do you differentiate between user-defined variables and NM-defined 
variables? [~Jim_Brennan] and [~jlowe] can correct me if I'm wrong on our 
current approach with YARN-7677, but I thought we were going with the following 
hierarchy: user-defined, image-defined, NM-defined. If something is NM-defined, 
but not user-defined, we want it to use the image-defined version. However, if 
it is user-defined, then we want the user-defined version. But, this is not 
possible by simply passing {{-e K=V}} on the {{docker run}} command line

> 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}
> {code}
> docker run [image]:[version]
> {code}

This message was sent by Atlassian JIRA

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