overlord address is set to unreachable container address

[prathamesh13]

While working with docker-druid image and tranquility library i found that the address stored under druid/discovery/druid:overlord in zookeeper is the container address as shown below:

{"name":"druid:overlord","id":"91bb6dbd-9b8c-4863-9530-e70c9f7f6587","address":" 172.17.0.2","port":8081,"sslPort":-1,"payload":null,"registrationTimeUTC":154416 6430226,"serviceType":"DYNAMIC","uriSpec":null}

This container address would be the one that an application using tranquility library would get from zookeeper through curator service discovery. Since this address is not the machine's reachable IP address data would not be sent to druid using tranquility.

The address is probably coming from supervisor.conf :
-Ddruid.host=%(ENV_HOSTIP)s

Should this be set to host machine's IP rather than container IP?

This issue appears to be related to druid-io/tranquility#186

Discussion on google groups:
https://groups.google.com/forum/#!topic/druid-user/TDBOaBNZXZQ
https://groups.google.com/forum/#!topic/druid-user/DAi5xfSrVhY
https://groups.google.com/forum/#!topic/druid-user/BHWbldJy1ks