These are chat archives for spring-cloud/spring-cloud

24th
Dec 2015
Bryan
@bla204
Dec 24 2015 12:48
I had followed that example to get my application launched and talking with the consul container. The issue hits that when I run the http api query to consul I appear to get the consul containers ip for every service rather than the docker hosts or other containers ip
Dave Syer
@dsyer
Dec 24 2015 12:54
Bryan
@bla204
Dec 24 2015 12:54
Actually it appears to return the service containers ip which does work for systems that are all running on that same network interface, but I was hoping for it to return the docker machines ip so external clients could access it
I did set that which fixed it from returning the machine name
Dave Syer
@dsyer
Dec 24 2015 12:55
Ah. That would explain why it works in the tests.
Dave Syer
@dsyer
Dec 24 2015 15:11
Docker networks are a bit of a moving target
Weave looks useful
Bryan
@bla204
Dec 24 2015 15:13
the current setup is working now as long as you know the endpoint you want to access without consul
i will look at weave
https://github.com/weaveworks/weave is this what you are referring to?
Dave Syer
@dsyer
Dec 24 2015 15:32
Yes
You probably don't even need service discovery with that