Forcing IP address doesn't work about registrator HOT 11 CLOSED

Consul overrides the IP, so that option doesn't work with that backend. Key
value works though. Consul should fix this soon.

On Wednesday, September 17, 2014, Daniel Schierbeck <
[email protected]> wrote:

I'm having trouble forcing the IP address of the services to be the host's
address rather than the consul container's. I'm launching the registrator
container like this:

docker run --rm -v /var/run/docker.sock:/tmp/docker.sock --name registrator.1 --link consul.1:consul progrium/registrator -ip 192.168.140.2 consul://consul:8500

... yet all the services are defined with the consule container's IP
anyway. It actually took me a while to realize that the IP and port of the
services corresponded to the host rather than the containers themselves.

Am I doing something wrong?

—
Reply to this email directly or view it on GitHub
https://github.com/progrium/registrator/issues/23.

Jeff Lindsay
http://progrium.com

from registrator.

@dasch : If it can help, for now, I mitigate that issue by starting progrium/docker-consul using the -net=host switch. This cause consul to bind to the host IP.

Which end up with registrator registering it's service under the (host) IP you are expecting. This also make starting consul a bit more straigtforward, ex:

docker run --net=host --name consul progrium/consul-docker -server -bootstrap

from registrator.

@pfcarrier that worked, thanks! I had to run registrator on the host net as well.

from registrator.

Is there a link to the issue on the consul repo?

from registrator.

hashicorp/consul#229

from registrator.

Is there a way to force a service IP address to be the service container's IP?

It seems the only options with consul are service-IP==consul-IP or service-IP==host-IP

from registrator.

I fixed this by running -advertise PUBLICIP when launching your docker consul container.

from registrator.

Can this be fixed yet? The -advertise trick works fine as long as all the service containers are running on the same Docker host as the Consul container.

But if you're running registrator on a different Docker host than the one Consul is on, the IP is wrong again.

HTTP API supports setting a custom IP per service now, so is it possible? Thanks!

from registrator.

You can force the IP with -ip. And yes it works with Consul now. I think only in master though.

from registrator.

Aha. Yes, after switching to master -ip works fine. This is great.

from registrator.

Fixed by #91 (Currently only in master.)

from registrator.