Jim Brennan commented on YARN-7654:

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?

If the docker image defines one of the values listed in the nodemanager 
whitelist, and the user does not override it, the nodemanager value will be 
passed in via -e K=V, and that will override the value defined in the docker 
image.   This would be a difference in behavior compared with the 
non-entry-point images (after [YARN-7677] goes in.

> 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