Apache
/
hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

YARN-8624. Updated verbiage around entry point support. 

Contributed by Craig Condit
This commit is contained in:
Eric Yang 2018-08-06 12:37:59 -04:00
parent bcfc9851f4
commit ca20e0d7e9
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/DockerContainers.md
View File

@ -316,15 +316,11 @@ set, the behavior will depend on whether the
the command will be overridden when LCE launches the image with YARN's
container launch script.
If a Docker image has an
[entry point](https://docs.docker.com/engine/reference/builder/#entrypoint)
set, the entry point will be honored, but the default command may be
overridden, as just mentioned above. Unless the entry point is
something similar to `sh -c` or
`YARN_CONTAINER_RUNTIME_DOCKER_RUN_OVERRIDE_DISABLE` is set to true, the net
result will likely be undesirable. Because the YARN container launch script
is required to correctly launch the YARN task, use of entry points is
discouraged.
If a Docker image has an entry point set and
YARN_CONTAINER_RUNTIME_DOCKER_RUN_OVERRIDE_DISABLE is set to true,
launch_command will be passed to ENTRYPOINT program as CMD parameters in
Docker. The format of launch_command looks like: param1,param2 and this
translates to CMD [ "param1","param2" ] in Docker.
If an application requests a Docker image that has not already been loaded by
the Docker daemon on the host where it is to execute, the Docker daemon will