Thomas,
- 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 container ports and that you use a
> direct mapping (hostport n <-> same container port n), is that
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 a CNI port mapper plugin (DNAT) in Mesos
On 03/31/2017 10:23 AM, Tomek Janiszewski wrote:
> I have a question that is related to this topic. In "docker support
> and current limitations" section [1] there is a following statement:
> > Only host network is supported. We will add bridge network support
> soon using CNI support in Mesos
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
I have a question that is related to this topic. In "docker support and
current limitations" section [1] there is a following statement:
> Only host network is supported. We will add bridge network support soon
using CNI support in Mesos (MESOS-4641
Cool, looking forward to it!
On Fri, Mar 31, 2017 at 4:30 AM, tommy xiao wrote:
> Alex,Yes, let me have a try.
>
> 2017-03-31 3:16 GMT+08:00 Alex Rukletsov :
>
>> This is https://issues.apache.org/jira/browse/MESOS-7210. Deshi, do you
>> want to send the
6 matches
Mail list logo