3 ms·
One new 2.0 feature you may like (discovery wise) is SRV discovery, if you've got an internal DNS/dnsmasq or something. Set a few records for where machines can
by barakm 12y ago
One new 2.0 feature you may like (discovery wise) is SRV discovery, if you've got an internal DNS/dnsmasq or something. Set a few records for where machines can be found (and keep them appropriately up to date) and it'll do the same thing as a static bootstrap automatically
- lclarkmichalek 12y agoUnfortunately, I run skydns for service discovery, and having multiple dns servers on the same machine is a PITA. I should note, for anyone considering skydns, that skydns + etcd + docker is circular dependency hell :)
- saryant 12y agoWhat problems have you had? We're using a similar setup but SkyDNS has been pretty trouble-free so far.
- lclarkmichalek 12y agoIf skydns fails to load its config from etcd, it doesn't terminate, it just continues and emits a warning. If you are using etcd.discovery.io for your discovery url, you need to have dns working. At some point, passing multiple --dns to docker didn't cause failover to be working. Or at least, dns resolution was failing in the etcd container, despite the docker daemon having `--dns 127.0.0.1 --dns 8.8.8.8 --dns 8.8.4.4`. I don't even know.