Hi! I’m trying Spring Cloud Consul with overlay Docker networks, and I face a problem because my Consul doesn’t have access to the containers running on my cluster, since they are being advertised with ip’s like 10.x.x.x, so Consul always thinks that they are down. I guess it’d fixed if spring cloud clients would advertise themselves using the host IP, but I’m not sure if that’s possible. How do you guys approach this?
I believe it would involve setting spring.cloud.consul.discovery.preferIpAddress=true and setting SPRING_CLOUD_CONSUL_DISCOVERY_IP_ADDRESS to the correct ip when you start the container. @marcingrzejszczak may have a better idea.
Hi guys, I’m playing spring cloud config server and spring cloud bus and sometimes my configserver doesn’t update the local copy of my git repository. Is that a known issue? I’m using Angel.SR6 version.