Registrator not listening to docker events

Consul is running fine

Registrator is running fine, but it’s not listening to docker events.

  • Huge files in Docker containers
  • How to read files and stdout from a running Docker container
  • Docker - running commands from all containers
  • docker push to dockerhub private repo sometimes pushes existing layer again (ubuntu base layer)
  • Assign port to container
  • Unable to download docker golang image: No command specified
  • ran registrator as :

    docker run -d -h -v /var/run/docker.sock:/tmp/docker.sock progrium/registrator consul://

    also tried

    docker run -d -h -P -v /var/run/docker.sock:/tmp/docker.sock progrium/registrator consul://

    docker logs 73acf7b7f687b6c02e35ccfa6e2a41e42eea18a27292befd87d65fc665d20320
    2014/10/07 21:39:49 registrator: Using consul registry backend at consul://

    But not “Listening to docker events”

    help please.

  • Cyclic backups of a docker postgresql container
  • Memory usage of Docker containers
  • Docker-machine ip in Dockerfile
  • Docker: Host not found in upstream app:9000
  • Could not save file in the docker image after “docker commit”
  • AWS docker set --no-cache flag
  • One Solution collect form web for “Registrator not listening to docker events”

    I had a somewhat similar issue with etcd. Before listening for new events, registrator tries registering the services which are already running. I don’t know much about consul (and did not know much about etcd either) but looking at the http communication give me the hint what was going wrong. Try

    tcpdump -i any -A -s 0 host 

    Assuming you see traffic, watch closely to the response of consul. I would expect it to respond with HTTP error codes which may point you to the root cause. If you don’t see traffic, double check addresses and iptable configuration.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.