[
https://issues.apache.org/jira/browse/MESOS-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Buffington updated MESOS-1761:
----------------------------------
Description:
When I specify an ExecutorInfo with a ContainerInfo set, the docker
containerizer will do {{docker run ... /bin/sh -c ./my-executor}}.
If the docker image the user specifies has an entrypoint configured the
executor command will be appended to the entrypoint rather than overwriting it.
The docker docs says:
{quote}
Unlike the behavior of the CMD instruction, The ENTRYPOINT instruction adds an
entry command that will not be overwritten when arguments are passed to docker
run. This allows arguments to be passed to the entry point, i.e. docker run
<image> -d will pass the -d argument to the entry point.
{quote}
This results in docker running the entrypoint inside the container with the
executorinfo's command as an argument. If you specified an executor this is
never what you want.
I suggest docker run use {{--entrypoint}} when starting an executor inside the
container.
was:
cWhen I specify an ExecutorInfo with a ContainerInfo set, the docker
containerizer will do {{docker run ... /bin/sh -c ./my-executor}}.
If the docker image the user specifies has an entrypoint configured the
executor command will be appended to the entrypoint rather than overwriting it.
The docker docs says:
{quote}
Unlike the behavior of the CMD instruction, The ENTRYPOINT instruction adds an
entry command that will not be overwritten when arguments are passed to docker
run. This allows arguments to be passed to the entry point, i.e. docker run
<image> -d will pass the -d argument to the entry point.
{quote}
This results in docker running the entrypoint inside the container with the
executorinfo's command as an argument. If you specified an executor this is
never what you want.
I suggest docker run use {{--entrypoint}} when starting an executor inside the
container.
> docker containerizer should override entrypoint when starting executor.
> -----------------------------------------------------------------------
>
> Key: MESOS-1761
> URL: https://issues.apache.org/jira/browse/MESOS-1761
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Reporter: Jay Buffington
> Assignee: Timothy Chen
> Labels: docker
> Fix For: 0.20.1
>
>
> When I specify an ExecutorInfo with a ContainerInfo set, the docker
> containerizer will do {{docker run ... /bin/sh -c ./my-executor}}.
> If the docker image the user specifies has an entrypoint configured the
> executor command will be appended to the entrypoint rather than overwriting
> it. The docker docs says:
> {quote}
> Unlike the behavior of the CMD instruction, The ENTRYPOINT instruction adds
> an entry command that will not be overwritten when arguments are passed to
> docker run. This allows arguments to be passed to the entry point, i.e.
> docker run <image> -d will pass the -d argument to the entry point.
> {quote}
> This results in docker running the entrypoint inside the container with the
> executorinfo's command as an argument. If you specified an executor this is
> never what you want.
> I suggest docker run use {{--entrypoint}} when starting an executor inside
> the container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
