I have set up 2 CoreOS machines in Azure. both run the Rancher agent.
They are visible in the Rancher UI and I can deploy containers to it.
On one machine, I have deployed Ubuntu and linked it to a Http Service on the other machie.
The Ubuntu container can see the other machine, so the network seems correct so far.
$ ping cow1 <-- that is the other machine
PING cow1.rogerrancher.a1.internal.cloudapp.net (192.168.0.6) 56(84) bytes of da
ta.
64 bytes from 192.168.0.6: icmp_seq=1 ttl=63 time=6.96 ms
But it cannot see the http service, it fails with a message “No route to host”
$ ping httpservice <-- that is the linked service on cow1
PING httpservice.rancher.internal (10.42.173.246) 56(84) bytes of data.
From 10.42.151.125 icmp_seq=1 Destination Host Unreachable
The services runs with the default Rancher managed network (httpservice.rancher.internal (10.42.173.246) )
This is probably not at all related to Rancher but rather my lack of Linux knowledge.
But any pointers would be welcome here.
I have also set up the exact same topology locally but running RancherOS, and with this configuration, the linked containers can see eachother without any issues.
Is there something that RancherOS does that CoreOS don’t do out of the box when it comes to networking?
Anyone?