hmalphettes / docker-route53-dyndns Goto Github PK

Hi,

I'm trying to register my containers to a private zone but am receiving a cryptic error and not sure what the problem is:

$ docker run --rm --name route53 -v /var/run/docker.sock:/tmp/docker.sock -v /root/.aws:/root/.aws -e PUBLIC_IP=$(hostname -i) -e DRY_ROUTE53=true -e PRIVATE_TOP_ZONES=staging.aws -t hmalphettes/docker-route53-dyndns /usr/local/bin/docker-gen -watch -notify "/bin/sh -x /tmp/cli53routes" /app/cli53routes.tmpl /tmp/cli53routes
2015/08/26 21:03:00 Generated '/tmp/cli53routes' from 3 containers
2015/08/26 21:03:00 Running '/bin/sh -x /tmp/cli53routes'
2015/08/26 21:03:00 Error running notify command: /bin/sh -x /tmp/cli53routes, exit status 1
2015/08/26 21:03:00 + [ -z 10.1.20.102 ]
+ [ -z 10.1.20.102 -o not found = 10.1.20.102 ]
+ [ -z staging.aws ]
2015/08/26 21:03:00 Watching docker events

Please note that only 1 of my containers has VIRTUAL_HOST variable set and it is set to VIRTUAL_HOST=amqp.staging.aws

I also get the same error without the dry run option.

Thanks for your help!

Yannis

I'd like to use this with with route53 alias or cname records pointing to an ELB.

I'd prefer to handle nginx routing on my own. Is this possible?

Also, an ideal use case for me would be delegating 2 records to the container. One an A record or CNAME on the private hosted zone (I say cname because the underlying host already has an A record, so an alias record pointing to it is preferable). The other being an optional public ALIAS or CNAME to an ELB or router node.

I have a hosted zone that is xxx.id.au and i assume there are many other 3rd level domains out there. Any chance you could modify this to compare the VIRTUAL_HOST to the list of hosted zones and find the match based on the VIRTUAL_HOST ending with the hosted zone?

If it is too hard i will buy another domain name because this container makes things so much easier. fantastic idea.