[
https://issues.apache.org/jira/browse/YARN-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384187#comment-16384187
]
Eric Yang commented on YARN-7654:
---------------------------------
[~Jim_Brennan] Yes, this is partially true. The actual behavior difference
depends on ENTRY_POINT. If the launching process is reconstructing user
environment for child process. There is nothing that container-executor can do
to prevent it. The parent layer (container-executor) provide the same
information to the first process in docker. The observed behavior is caused by
how the docker image was originally constructed, not caused by different code
path leading to the difference in behavior. As long as we show the execution
command clearly in container log, I think it is easy for programmers to
identify the root causes of difference in behavior. Thoughts?
> 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: [email protected]
For additional commands, e-mail: [email protected]
