Mesos-docker-executor understanding

ificality relative to the mesos-executor ? Thanks -- Thomas HUMMEL

Re: Mesos (and Marathon) port mapping

understanding : Thanks. On 04/05/2017 12:23 PM, Thomas HUMMEL wrote: Ok, thanks. So if I wrap my head around all of this and try to answer my original question I come up with the following understanding : - servicePorts a a Marathon only concept - port mapping isolator is not compatible with docker

Re: Mesos (and Marathon) port mapping

On 03/31/2017 07:51 PM, Jie Yu wrote: Tomek and Olivier, The bridge network support (with port mapping) has been added to Mesos 1.2. See this doc for more details how to use it: https://github.com/apache/mesos/blob/master/docs/cni.md#a-port-mapper-plugin-for-cni-networks TL;DR: we developed

Re: Mesos (and Marathon) port mapping

Ok, thanks. So if I wrap my head around all of this and try to answer my original question I come up with the following understanding : - servicePorts a a Marathon only concept - port mapping isolator is not compatible with docker containerizer - port mapping isolator is useful when you

Re: Mesos (and Marathon) port mapping

Thanks for your answer, I've watched your talk. Very interesting. Let me check if I get everything staight : - it is the hostports which are used to multiplex traffic into container. My understanding is that, since each container is in it's network namespace, it has its own full range of

Re: Mesos (and Marathon) port mapping

On 03/29/2017 07:25 PM, Jie Yu wrote: Thomas, I think you are confused about the port mapping for NAT purpose, and the port mapping isolator . Those two very different thing. The port mapping isolator (unfortunate

Re: Mesos (and Marathon) port mapping

On 03/29/2017 01:21 PM, Dick Davies wrote: I should say this was tested around mesos 1.0, they may have changed things - but yes this is vanilla networking, no CNI or anything like that. As a matter of fact, that's what I experience. But I'm guessing if you're using BRIDGE networking and

Re: Mesos (and Marathon) port mapping

Also, does network/portmapping isolator makes sense if the containerizer is docker ?

Re: Mesos (and Marathon) port mapping

a bit confused since what's described here http://mesos.apache.org/documentation/latest/port-mapping-isolator/ in the "Configuring network ports" seems to be valid even without port mapping isolator. Am I getting this right this time ? Thanks. -- Thomas HUMMEL

Mesos (and Marathon) port mapping

root6u IPv4 461745 0t0 TCP *:websm (LISTEN) But Marathon tells that my app is running on : mesos-slave1.it.pasteur.fr:31830 I don't understand where this port comes from, especially when I see nobody's listening on it : lsof -i :31830 like if Marathon gave me a fake hostPort ? 4. My understanding is that Marathon service port are bound to only by apps like marathon-lb. As a matter of fact, it doesn't seem to bother Mesos that Marathon deploys 2 apps on the same slave with the same servicePort. Am I correct ? Thanks for your help -- Thomas HUMMEL