You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Ezra Silvera (JIRA)" <ji...@apache.org> on 2016/01/19 18:56:39 UTC

[jira] [Updated] (MESOS-4369) Enhance DockerExecuter to support Docker's user-defined networks

     [ https://issues.apache.org/jira/browse/MESOS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ezra Silvera updated MESOS-4369:
--------------------------------
    Summary: Enhance DockerExecuter to support Docker's user-defined networks  (was: Enhance DockContainerizer to support Docker network created with Docker CLI)

> 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
>
> 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)