You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2014/09/04 23:14:23 UTC

[jira] [Assigned] (MESOS-1621) Docker run networking should be configurable

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

Timothy Chen reassigned MESOS-1621:
-----------------------------------

    Assignee: Timothy Chen

> Docker run networking should be configurable
> --------------------------------------------
>
>                 Key: MESOS-1621
>                 URL: https://issues.apache.org/jira/browse/MESOS-1621
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Timothy Chen
>            Assignee: Timothy Chen
>              Labels: Docker
>
> Currently to easily support running executors in Docker image, we hardcode --net=host into Docker run so slave and executor and reuse the same mechanism to communicate, which is to pass the slave IP/PORT for the framework to respond with it's own hostname and port information back to setup the tunnel.
> We want to see how to abstract this or even get rid of host networking altogether if we have a good way to not rely on it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)