Consul services seem to be registered under wrong node about registrator HOT 13 CLOSED

Same for me - I'd like to get rid of the overhead for running consul-agent on the whole coreos cluster.
Registrator would be the perfect fit since it's located on all machines anyway.

from registrator.

Tried multiple times and this always happens if I register against a consul server IP. I was only able to get registrator to work by using the docker socket IP and also running the consul-agent in a sidecar container

from registrator.

I noticed the same behavior and it appears to be intentional. If you look at the consul registration code it only creates a "service" entry via the target consul agent. From what I can tell (though I'm hardly a consul expert) this type of entry does not have an associated IP address, rather it is associated with a "node" in consul which is what holds the Host/IP of the service. When you register a service directly with the agent that agent becomes the service's node -- thus any service you register will appear as if it is running on the agent's host. As a result you need to do what you suggest and run a consul sidecar on every host where you register Docker services.

From what I can tell it would be possible for the registration code to register both a Node and a Service so that even hosts without a consul agent could contain services. Doing so (or providing the option to do so) would make it work more like SkyDNS/Etcd both of which do register host and port.

from registrator.

Do you have any eta for this ?

Thanks.

from registrator.

Im trying to loadbalance between dockers on the same host, is it possible to advertise the docker ip in any way?

from registrator.

@fliphess you can do something like that using the -internal switch when using etcd as a backend. But at the moment, Consul will only register services under its IP.

from registrator.

I've made a kind of solution, it is testable.
Github: https://github.com/enpassant/registrator
Docker: https://registry.hub.docker.com/u/enpassant/registrator/

from registrator.

Did merging PR #93 fix this then?

from registrator.

What was the outcome of this? Due to the bug with docker/consul and arp caching I've got to run my consul instance with -net=host. Now all of my docker containers get registered with the private ip of the docker host, rather than the private ip of the docker containers.

moby/moby#4581
gliderlabs/docker-consul#26

from registrator.

It seems that this registrator aims at register service at local agent, so maybe you need to run a agent on 10.10.2.55 and change the registrator url to consul://10.10.2.55:8500

from registrator.

Yeah, you should either run the Consul agent locally (it's intended to be run on all hosts), but I believe the latest version will use the IP that Registrator determines (which is best set with -ip).

See docs:
http://gliderlabs.com/registrator/latest/user/run/

Reopen if still an issue.

from registrator.

I am seeing this occur even if registrator has the -ip flag set.

from registrator.

Same problem here, also with -ip flag - works fine when using local consul.

from registrator.