You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
However, container doesn't know it's own hostname:
Can container get its own hostname from dns and use it?
The text was updated successfully, but these errors were encountered: