YARN-8624. Updated verbiage around entry point support.
Contributed by Craig Condit
This commit is contained in:
parent
bcfc9851f4
commit
ca20e0d7e9
|
@ -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
|
the command will be overridden when LCE launches the image with YARN's
|
||||||
container launch script.
|
container launch script.
|
||||||
|
|
||||||
If a Docker image has an
|
If a Docker image has an entry point set and
|
||||||
[entry point](https://docs.docker.com/engine/reference/builder/#entrypoint)
|
YARN_CONTAINER_RUNTIME_DOCKER_RUN_OVERRIDE_DISABLE is set to true,
|
||||||
set, the entry point will be honored, but the default command may be
|
launch_command will be passed to ENTRYPOINT program as CMD parameters in
|
||||||
overridden, as just mentioned above. Unless the entry point is
|
Docker. The format of launch_command looks like: param1,param2 and this
|
||||||
something similar to `sh -c` or
|
translates to CMD [ "param1","param2" ] in Docker.
|
||||||
`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 an application requests a Docker image that has not already been loaded by
|
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
|
the Docker daemon on the host where it is to execute, the Docker daemon will
|
||||||
|
|
Loading…
Reference in New Issue