[
https://issues.apache.org/jira/browse/MESOS-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070968#comment-14070968
]
Timothy Chen commented on MESOS-1621:
-------------------------------------
I'm explicitly trying to avoid just args override in general because it makes
transitioning to another implementation quite difficult as we no longer know
what breaks for people, makes limiting options more hassle, also we need to
handle a lot more cases when the user passes in configuration that can break
things (--name test).
Although we have flexibility to allow users to use more docker features as
they're ready there are too much cost to pay with that IMO.
Let me know think if you have other thoughts.
> 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
> 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.2#6252)
