mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "z s (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-9269) Mesos UCR with Docker only Works on Localhost
Date Thu, 27 Sep 2018 04:44:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-9269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629747#comment-16629747
] 

z s edited comment on MESOS-9269 at 9/27/18 4:43 AM:
-----------------------------------------------------

The last line seems to imply that the nat rule is correct. The service is assigned to port
22555 on the host machine.
{code:java}
Chain MESOS-BRIDGE-PORT-MAPPER (2 references) target     prot opt source          
    destination          DNAT       tcp  --  anywhere             anywhere
            tcp dpt:22555 /* container_id: 48d3e3f9-9d37-4da7-9011-586138cd5e74 */ to:10.1.0.3:22555

{code}
 

ifconfig on host:

 
{code:java}
mesos-cni0 Link encap:Ethernet  HWaddr e6:96:93:6a:f4:1d 
          inet addr:10.1.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          inet6 addr: fe80::e496:93ff:fe6a:f41d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:196 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:17473 (17.4 KB)  TX bytes:6322 (6.3 KB)
{code}
 

 ifconfig from inside the container also seems to be consistent: 
{code:java}
eth0 Link encap:Ethernet HWaddr 5E:43:B2:17:A3:2F 
 inet addr:10.1.0.3 Bcast:0.0.0.0 Mask:255.255.0.0
 inet6 addr: fe80::5c43:b2ff:fe17:a32f/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:24 errors:0 dropped:0 overruns:0 frame:0
 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0 
 RX bytes:5832 (5.6 KiB) TX bytes:2975 (2.9 KiB)
lo Link encap:Local Loopback 
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1 
 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
{code}
 

 


was (Author: dkjs):
The last line seems to imply that the nat rule is correct:

 
{code:java}
Chain MESOS-BRIDGE-PORT-MAPPER (2 references) target     prot opt source          
    destination          DNAT       tcp  --  anywhere             anywhere
            tcp dpt:22555 /* container_id: 48d3e3f9-9d37-4da7-9011-586138cd5e74 */ to:10.1.0.3:22555

{code}
The service is assigned to port 22555 on the host machine. ifconfig from inside the container
also seems to be consistent:

 
{code:java}
eth0 Link encap:Ethernet HWaddr 5E:43:B2:17:A3:2F 
 inet addr:10.1.0.3 Bcast:0.0.0.0 Mask:255.255.0.0
 inet6 addr: fe80::5c43:b2ff:fe17:a32f/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:24 errors:0 dropped:0 overruns:0 frame:0
 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0 
 RX bytes:5832 (5.6 KiB) TX bytes:2975 (2.9 KiB)
lo Link encap:Local Loopback 
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:65536 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1 
 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
{code}
 

 

> Mesos UCR with Docker only Works on Localhost
> ---------------------------------------------
>
>                 Key: MESOS-9269
>                 URL: https://issues.apache.org/jira/browse/MESOS-9269
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent, docker
>    Affects Versions: 1.7.0
>         Environment: Ubuntu 16.04
> Mesos 1.7.0
> Marathon 1.7.111
>            Reporter: z s
>            Priority: Major
>
> I'm having an issue setting up the `mesos-cni-port-mapper` to allow remote connectivity.
> When I `curl <host>:<port>` from the machine I get a response but from a
remote machine the `curl` connection timesout. I'm not sure what's wrong with my route settings.
>  
> */var/lib/mesos/cni/config/mesos-bridge.json*
>  
> {code:java}
> {
> "name" : "mesos-bridge",
> "type" : "mesos-cni-port-mapper",
> "excludeDevices" : ["mesos-cni0"],
> "chain": "MESOS-BRIDGE-PORT-MAPPER",
> "delegate": {
> "type": "bridge",
> "bridge": "mesos-cni0",
> "isGateway": true,
> "ipMasq": true,
> "ipam": {
> "type": "host-local",
> "subnet": "10.1.0.0/16",
> "routes": [
> { "dst":
> "0.0.0.0/0" }
> ]
> }
> }
> }
> {code}
>  
> {code:java}
> $ route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 172.27.1.1 0.0.0.0 UG 0 0 0 ens3
> 10.1.0.0 0.0.0.0 255.255.0.0 U 0 0 0 mesos-cni0
> 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
> 172.27.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ens3
> {code}
> Any suggestions?
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message