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

z s edited comment on MESOS-9269 at 9/27/18 1:26 AM:
-----------------------------------------------------

It seems like it's actually an application issue with the IP binding, not sure 
the reason why though. 

Explicitly binding to 0.0.0.0 does not work
{code:java}
python3 -m http.server --bind 0.0.0.0 $PORT0
{code}
vs
{code:java}
python3 -m http.server $PORT0
{code}
(the later appears to work without issue).

 

Is there an explaination for this? By default all of our docker services bind 
to 0.0.0.0 to accept all incoming traffic. After trying to switch over to the 
Mesos UCR we see this strange behavior.


was (Author: dkjs):
It seems like it's actually an application issue with the IP binding, not sure 
the reason why though. 

Explicitly binding to 0.0.0.0 does not work
{code:java}
python3 -m http.server --bind 0.0.0.0 $PORT0
{code}
vs
{code:java}
python3 -m http.server $PORT0
{code}
(the later appears to work without issue)

> 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)

Reply via email to