[
https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132154#comment-14132154
]
Timothy St. Clair commented on MESOS-1621:
------------------------------------------
Having a fully managed interface is always useful from programmatic
perspective, however after lots of thought...
I still think it useful to have some form of command line override. Otherwise
as the interface to docker changes, we will constantly need to version track
and manage vs. creating a pass-through that empowers the user.
Thoughts?
> 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)
