[
https://issues.apache.org/jira/browse/YARN-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380374#comment-16380374
]
Shane Kumpf edited comment on YARN-7654 at 2/28/18 2:26 PM:
------------------------------------------------------------
Thanks [~eyang]! - overall I do feel this will improve the process.
Couple of questions:
* Will we eliminate setting the workdir in this model and leave that up to the
image? This has been a complaint I've heard with the bring your own image model.
* What is the impact on bind mounts? Will this help eliminate any of the
read-write mounts?
* Would it also be possible to support arguments passed into the container's
entrypoint? For instance, the Dockerfile ENTRYPOINT is ["ping"], the CMD is
["google.com"] and instead of pinging www.google.com, I want to "ping
www.yahoo.com" - the {{docker run}} would be {{docker run ... -e K=V \-e K=V
[image-name] www.yahoo.com}}.
Excited to see this make progress. :)
was (Author: shaneku...@gmail.com):
Thanks [~eyang]! - overall I do feel this will improve the process.
Couple of questions:
* Will we eliminate setting the workdir in this model and leave that up to the
image? This has been a complaint I've heard with the bring your own image model.
* What is the impact on bind mounts? Will this help eliminate any of the
read-write mounts?
* Would it also be possible to support arguments passed into the container's
entrypoint? For instance, the Dockerfile ENTRYPOINT is ["ping"], the CMD is
["google.com"] and I instead of pinging www.google.com, I want to "ping
www.yahoo.com" - the {{docker run}} would be {{docker run ... -e K=V \-e K=V
[image-name] www.yahoo.com}}.
Excited to see this make progress. :)
> 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
