[ https://issues.apache.org/jira/browse/MESOS-9269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631209#comment-16631209 ]
z s commented on MESOS-9269: ---------------------------- Setting the following rules seems to have helped: # sudo iptables -D DOCKER-ISOLATION-STAGE-2 -j RETURN # sudo iptables -I DOCKER-ISOLATION-STAGE-2 1 -j RETURN See [Marathon Jira|https://issues.apache.org/jira/browse/MESOS-9269?focusedCommentId=16631202&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16631202] > Mesos UCR with Docker only Works on Host > ---------------------------------------- > > 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)