[
https://issues.apache.org/jira/browse/MESOS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098695#comment-15098695
]
Ezra Silvera edited comment on MESOS-4369 at 1/14/16 7:34 PM:
--------------------------------------------------------------
[~clinta] not really. You need to change the executer code as well because it
is building the --net that is passed to the run command according to what was
passed in the task. So you'll end up with two different --net phrases on the
run command.
Also the executer adds the ports to the run command only for "bridge" mode . So
the user will have to pass --net=bridge if he wants also some port mapping
was (Author: ezrasilvera):
[~clinta] not really. You need to change the executer code as well because it
is building the --net that is passed to the run command according to what was
passed in the task. So you'll end up with two --net phrases on the run command.
Also the executer adds the ports to the run command only for "bridge" mode . So
the user will have to pass --net=bridge
> Enhance DockContainerizer to support Docker network created with Docker CLI
> ---------------------------------------------------------------------------
>
> Key: MESOS-4369
> URL: https://issues.apache.org/jira/browse/MESOS-4369
> Project: Mesos
> Issue Type: Improvement
> Components: docker
> Reporter: Qian Zhang
>
> Currently DockerContainerizer supports the following network options which
> are Docker built-in networks:
> {code}
> message DockerInfo {
> ...
> // Network options.
> enum Network {
> HOST = 1;
> BRIDGE = 2;
> NONE = 3;
> }
> ...
> {code}
> However, with Docker CLI, user can create a customized network, e.g.,
> {{docker network create my-network}}, we need to enhance DockerContainerizer
> to support such network so that the Docker container that user creates in
> Mesos with DockerContainerizer can connect into such network.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
