[
https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127390#comment-14127390
]
Meghdoot Bhattacharya commented on MESOS-1621:
----------------------------------------------
Timothy, the approach makes sense because we want in general mesos/framework to
select the ports from the offer and not docker daemon. One question I had is if
the docker tasks are killed, are the ports released back into the offer, or are
they lost? This applies to tasks in MesosContainerizer as well.
> Docker run networking should be configurable and support bridge network
> -----------------------------------------------------------------------
>
> Key: MESOS-1621
> URL: https://issues.apache.org/jira/browse/MESOS-1621
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> 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)
