You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Nimi Wariboko Jr. (JIRA)" <ji...@apache.org> on 2019/03/03 08:06:00 UTC

[jira] [Commented] (MESOS-9269) Mesos UCR with Docker only Works on Host

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

Nimi Wariboko Jr. commented on MESOS-9269:
------------------------------------------

I recently ran into this issue as well - I could only access the mesos container image from the host but not remotely. I noticed in my case that the issue went away when I didn't have docker installed on the agent. If I installed the agent with iinstalling docker (and disabling the docker containerizer), everything worked as expected.

I also imagine this is why the DC/OS install worked fine - maybe the DC/OS agents do not have docker installed.

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