Closed BostonDriver closed 8 years ago
I would second this as a feature I actually need today. The ability to call docker on a marathon application build and create network overlays at the same time would be handy. Use cases that come to mind would be launching all containers in an app into an on the fly created calico net.
I looks like this is also needed for mesos unified containers as well as docker.
Any one have anything to report on asking for this feature? I've got to write an interface for this and I'd love to find a workaround.
we can use marathon docker parameter to --net=customernet
marathon now supports docker user networks. use docker network type USER and ipAddress.networkName=the-name-of-your-user-network
@jdef , so the user story suggests:
doesn't it?
yes that sounds about right
On Sun, Aug 28, 2016 at 9:36 PM, Zhou Weitao notifications@github.com wrote:
@jdef https://github.com/jdef , so the user story suggests:
- create the user-defined network somewhere outside of the mesos/marathon
- call the marathon interface with params: docker network type&ipAddress sth.
doesn't it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mesosphere/marathon/issues/3788#issuecomment-243014236, or mute the thread https://github.com/notifications/unsubscribe-auth/ACPVLL4jOlkF0GQ35LSZv0-N29I91LNaks5qkjeogaJpZM4II7lh .
+1
Marathon doesn't allow docker user-defined networks to be used. Mesos added this support via https://issues.apache.org/jira/browse/MESOS-4369. Example json showing how to specify the user-defined network will also help.