You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
I'm running several docker containers. One is used for Consul, running server and agent on the same machine. Another one is used for a Java service (Dropwizard) using the Java Docker image. To connect my Java service with Consul, I use dropwizard-consul. It is based on consul-client.
Since the Java container has its own IP address, but does not propagate it to Consul as service address, I don't have a valid service registration.
Consul uses the agents address as fallback, which is wrong in my case.
However, it's possible to specify a service address:
The address field can be used to specify a service-specific IP address. By default, the IP address of the agent is used, and this does not need to be provided.
(duplicate of #28, but it has never been reconsidered yet)
The text was updated successfully, but these errors were encountered:
I think the general use case is that people run the agent locally on the machine, so I'm guessing this is not a very common use case, and therefore probably not worth adding another set of overloaded registration methods to AgentClient
I'm running several docker containers. One is used for Consul, running server and agent on the same machine. Another one is used for a Java service (Dropwizard) using the Java Docker image. To connect my Java service with Consul, I use dropwizard-consul. It is based on consul-client.
Since the Java container has its own IP address, but does not propagate it to Consul as service address, I don't have a valid service registration.
Consul uses the agents address as fallback, which is wrong in my case.
However, it's possible to specify a service address:
(duplicate of #28, but it has never been reconsidered yet)
The text was updated successfully, but these errors were encountered: