search

mediadepot / chef-depot

DEPRECATED: Replaced by mediadepot/ignition
https://github.com/mediadepot/ignition
28 stars 2 forks source link

On the Host, figure out a way to resolve docker containers / lb entries #26

Closed AnalogJ closed 8 years ago

AnalogJ commented 8 years ago

https://github.com/gliderlabs/resolvable maybe? or the inernal rancher dns service.

AnalogJ commented 8 years ago

this is nice to have but not a requirement.. all dns resolution will be happening externally anyways.

AnalogJ commented 8 years ago

It seems that the "Network Agent" is a valid DNS server, which will allow us to make requests (from the host) with the following format (if 10.42.93.83 is the ip address of Network Agent container) 

dig guacweb.guacamole.rancher.internal @10.42.93.83
dig guacweb.guacamole @10.42.93.83
AnalogJ commented 8 years ago

potential issues: look at #25 which contains a magic ipaddress for the Rancher DNS server, probably only works within the Rancher network, but may be worth checking.

AnalogJ commented 8 years ago

docker network inspect bridge when used with docker ps (or API equivalents) could potnetially get you the ipaddress of the Rancher network agent, which could then be used for dns lookups.

AnalogJ commented 8 years ago

this was completed using the built in dnsmasq-base application installed by NetworkManager. wildcard dns lookups (default is *.depot)