issues with latest release
Closed this issue · 15 comments
With the latest release my containers aren't being registered with consul. If I checkout a random commit (856084a) and build, it works fine.
On a related note, can we get image tagging for new releases?
Thanks! Registrator is awesome :)
I'm going to need more information than that. And we do have versioned releases, please see the readme.
Not an issue. When providing the docker host as hostname, everything works fine. Pardon.
@NoumanSaleem please verify.
> docker run -d -p 8400:8400 -p 8500:8500 -p 8600:53/udp -h node1 --name consul progrium/consul -server -bootstrap -ui-dir /ui
> docker run -d -h 192.168.59.103 -v /var/run/docker.sock:/tmp/docker.sock --name registrator gliderlabs/registrator consul://192.168.59.103:8500
> docker run -d -P --name nginx nginx
> docker logs registrator
2015/02/20 01:28:22 registrator: Listening for Docker events...
2015/02/20 01:29:41 registrator: added: e6d833fd43fa 192.168.59.103:nginx:443
2015/02/20 01:29:41 registrator: added: e6d833fd43fa 192.168.59.103:nginx:80
@timmo will give it a shot. Sorry for the lack of info. Here is how my setup is currently, which doesn't work.
docker run --net=host -v /var/run/docker.sock:/var/run/docker.sock -p 8400:8400 -p 8500:8500 -p 53:53/udp -p 172.17.42.1:53:53/udp progrium/consul
docker run -h $HOSTNAME -v /var/run/docker.sock:/tmp/docker.sock progrium/registrator consul://consul:8500
There is another container with published ports, but no record of it in the logs
> docker ps
ad9dbe4c3dfe progrium/registrator:latest "/bin/registrator co 5 minutes ago Up 5 minutes progrium-registrator
f2294e1378b0 progrium/consul:latest "/bin/start -server 6 minutes ago Up 6 minutes progrium-consul
2b07565ac892 google/cadvisor:0.9.0 "/usr/bin/cadvisor" 7 minutes ago Up 7 minutes 0.0.0.0:8080->8080/tcp google-cadvisor
> docker logs ad9dbe4c3dfe
2015/02/20 16:20:14 registrator: Using consul registry backend at consul://consul:8500
2015/02/20 16:20:14 registrator v5 listening for Docker events...
2015/02/20 16:20:14 registrator: ignored: ad9dbe4c3dfe no published ports
2015/02/20 16:20:14 registrator: ignored: f2294e1378b0 no published ports
Can you try with gliderlabs/registrator:master?
On Fri, Feb 20, 2015 at 10:26 AM, Nouman Saleem notifications@github.com
wrote:
@timmo https://github.com/timmo will give it a shot. Sorry for the lack
of info. Here is how my setup is currently, which doesn't work.docker run --net=host -v /var/run/docker.sock:/var/run/docker.sock -p 8400:8400 -p 8500:8500 -p 53:53/udp -p 172.17.42.1:53:53/udp progrium/consul
docker run -h $HOSTNAME -v /var/run/docker.sock:/tmp/docker.sock progrium/registrator consul://consul:8500There is another container with published ports, but no record of it in
the logsdocker ps
ad9dbe4c3dfe progrium/registrator:latest "/bin/registrator co 5 minutes ago Up 5 minutes progrium-registrator
f2294e1378b0 progrium/consul:latest "/bin/start -server 6 minutes ago Up 6 minutes progrium-consul
2b07565ac892 google/cadvisor:0.9.0 "/usr/bin/cadvisor" 7 minutes ago Up 7 minutes 0.0.0.0:8080->8080/tcp google-cadvisordocker logs ad9dbe4c3dfe
2015/02/20 16:20:14 registrator: Using consul registry backend at consul://consul:8500
2015/02/20 16:20:14 registrator v5 listening for Docker events...
2015/02/20 16:20:14 registrator: ignored: ad9dbe4c3dfe no published ports
2015/02/20 16:20:14 registrator: ignored: f2294e1378b0 no published ports—
Reply to this email directly or view it on GitHub
#111 (comment)
.
Jeff Lindsay
http://progrium.com
It looks like it can't resolve consul
registrator:
vagrant@local:~$ docker exec -it ad9dbe4c3dfe sh
/ # ping consul
ping: bad address 'consul'
cadvisor:
vagrant@local:~$ docker exec -it 2b07565ac892 sh
/ # ping consul
PING consul (10.211.55.22): 56 data bytes
For some reason the container stopped respecting the docker dns-search setting. When starting the container with consul://consul.service.consul:8500 and not consul://consul:8500 it works
edit: using gliderlabs/registrator:master now
Well that wouldn't be registrator. Can you try to reproduce dns-search not working using the base image gliderlabs/alpine? And compare with progrium/busybox? That's the only change I know that would affect that.
Right on, there is the difference:
gliderlabs/alpine
vagrant@local:~$ docker run --rm -it gliderlabs/alpine sh
/ # ping consul
ping: bad address 'consul'
/ # ping consul.service.consul
PING consul.service.consul (10.211.55.22): 56 data bytes
64 bytes from 10.211.55.22: seq=0 ttl=64 time=0.045 ms
progrium/busybox
vagrant@local:~$ docker run --rm -it progrium/busybox
/ # ping consul
PING consul (10.211.55.22): 56 data bytes
vagrant@local:~$ cat /etc/default/docker
DOCKER_OPTS="--bip=172.17.42.1/16 --dns=172.17.42.1 --dns=10.0.2.15 --dns-search=service.consul"
Can you refile that particular issue against https://github.com/gliderlabs/docker-alpine ?
@progrium thanks, just did.
Besides that, how is :master working for you?
On Fri, Feb 20, 2015 at 10:53 AM, Nouman Saleem notifications@github.com
wrote:
@progrium https://github.com/progrium thanks, just did.
—
Reply to this email directly or view it on GitHub
#111 (comment)
.
Jeff Lindsay
http://progrium.com
@progrium Everything's running smooth against multiple upgrades docker: 1.5, consul: 0.5, latest registrator.
thanks!
I habe another issue with the latest release. Registrator doesn't seem to recognize the advertise option from consul any longer! All services are registered with the IP oft the consul container. I have set the advertise option to the docker0 ip. Is this also related to this issue?
@MattAitchison Yeah sure