-
Notifications
You must be signed in to change notification settings - Fork 241
consul health client timeout #180
Comments
Are you running your app container with --net=host? Otherwise localhost isn't going to work. |
There is a consul agent running inside the container so once the container starts up it registers its service. A curl inside the container to localhost works. |
Not sure what's going on here. I can't reproduce this. I'll look at the OK HTTP docs, but the Consuk code itself doesn't use IPv6 |
Can I help you with some additional information maybe? |
if you have more information to give, please do. |
Was this ever resolved? I'm having the same problem, would like to know if there's a workaround. |
Unfortunately not. This is the oldest item on my todo list but I'm not really sure where I could find more info. |
I am also running into this same issue with a dockerized consul agent running on the same host. edit: I figured out this issue and it had nothing to do with the library. I have the orbitz client running within my dockerized container. Everything is working as expected 👍 |
Hello,
I have an application that uses consul-client that is running fine on docker 1.11.2.
When deploying the same container to a docker with version 1.12 I get the message that it cannot connect tot the ipv6 address of localhost, which is normal because consul is running on ipv4 localhost.
When changing
consul = Consul.builder().build();
to
consul = Consul.builder().withUrl("http://127.0.0.1:8500").build();
one would assume it would take the correct address. Unfortunately this gives a timeout.
Is this an issue with the way the client connects to consul? Why is it trying to connect to ipv6?
The text was updated successfully, but these errors were encountered: