Thomas, I think you are confused about the port mapping for NAT purpose, and the port mapping isolator <http://mesos.apache.org/documentation/latest/port-mapping-isolator/>. Those two very different thing. The port mapping isolator (unfortunate naming), as described in the doc, gives you network namespace per container without requiring ip per container. No NAT is involved. I think for you case, you should not use it and it does not work for DockerContainerizer.
- Jie On Wed, Mar 29, 2017 at 2:22 AM, Thomas HUMMEL <[email protected]> wrote: > > > On 03/28/2017 06:53 PM, Tomek Janiszewski wrote: > > 1. Mentioned port range is the Mesos Agent resource setting, so if you > don't explicitly define port range it would be used. > https://github.com/apache/mesos/blob/1.2.0/src/slave/constants.hpp#L86 > > 2. With ports mapping two or more applications could attach to same > container port but will be exposed under different host port. > > > Thanks for your answer. > > 1. So it's not network/portmapping isolator specific, right ? Even without > it, non-ephemeral ports would be considered as part of the offer and would > be chosen in this range by default ? > > 2. So containers, even with network/port_mapping isolation, *share* the > non-ephemeral port range, although doc states "The agent assigns each > container a non-overlapping range of the ports" which I first read as "each > container gets it's own port range", right ? > > So I am 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 > >
