[
https://issues.apache.org/jira/browse/MESOS-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245052#comment-15245052
]
Qian Zhang commented on MESOS-5226:
-----------------------------------
The root cause of this bug is, in {{CommandScheduler::getContainerInfo()}}, we
will not return a {{ContainerInfo}} as long as there is no image specified even
there is CNI network specified, instead we will just return {{None()}} in this
case. And in {{NetworkCniIsolatorProcess::prepare()}}, we will just ignore the
container which has no {{ContainerInfo}}, so any CNI related logic will not be
applied to the executor which will be in agent host network namespace.
> The image-less task launched by mesos-execute can not join CNI network
> ----------------------------------------------------------------------
>
> Key: MESOS-5226
> URL: https://issues.apache.org/jira/browse/MESOS-5226
> Project: Mesos
> Issue Type: Bug
> Components: isolation
> Reporter: Qian Zhang
> Assignee: Qian Zhang
>
> With {{mesos-execute}}, if we launches a task which wants to join a CNI
> network but has no image specified, like:
> {code}
> sudo src/mesos-execute --master=192.168.122.171:5050 --name=test
> --networks=net1 --command="ifconfig" --shell=true
> {code}
> The corresponding command executor actually will not join the specified CNI
> network, instead it is still in agent host network namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
