Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to pass the SkyDNS/SkyDock hostnames as own hostnames into containers? #89

Open
vitalyisaev2 opened this issue Mar 20, 2015 · 1 comment

Comments

@vitalyisaev2
Copy link

First I would like to appreciate for a very useful services that you've developed. I managed to configure name resolution between Docker containers as it was proposed here.

Currently I have an urgent need to make container know its hostname assigned by SkyDNS.
When we launch a container inside Docker environment with SkyDNS+SkyDock enabled, it can be accessed with a fqdn:

isaev@wks-isaev:~$ docker run -d --name=test nginx
b48ff6a2b2718a05d4d307db17ff22f91c31ba8eb8b9c225b2e4bad375607ad3
isaev@wks-isaev:~$ dig @172.17.42.1 test.nginx.dev.skydns.local
...
;; ANSWER SECTION:
test.nginx.dev.skydns.local. 22 IN  A   172.17.0.100

However, container doesn't know it's own hostname:

isaev@wks-isaev:~$ docker exec test hostname --fqdn
b48ff6a2b271

Can container get its own hostname from dns and use it?

@dolanor
Copy link

dolanor commented Jun 29, 2015

Does the container's /etc/resolv.conf point to 172.17.0.1 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants