[
https://issues.apache.org/jira/browse/MESOS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213960#comment-15213960
]
Ezra Silvera commented on MESOS-4369:
-------------------------------------
I was waiting for the NetworkInfo to be merged. I just changed the code today
to use the new NetworkInfo and pushed a new patch
> Enhance DockerExecuter to support Docker's user-defined networks
> ----------------------------------------------------------------
>
> Key: MESOS-4369
> URL: https://issues.apache.org/jira/browse/MESOS-4369
> Project: Mesos
> Issue Type: Improvement
> Components: docker
> Reporter: Qian Zhang
> Assignee: Ezra Silvera
> Labels: mesosphere
>
> 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, since docker 1.9, Docker now supports user-defined networks (both
> local and overlays) - e.g., {{docker network create --driver bridge
> my-network}},. The user can then create containers that need to be attached
> to these networks e.g., {{docker run --net=my-network}},
> We need to enhance DockerExecuter to support such network option so that the
> Docker container that can connect into such network.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
