Docker 1.10 通过主机名从主机访问容器 [英] Docker 1.10 access a container by its hostname from a host machine
问题描述
我有带有嵌入式 DNS 服务的 Docker 1.10 版.
我在我的 docker-compose 文件中创建了两个服务容器.它们可以通过主机名和 IP 相互访问，但是当我想从主机访问其中一个时，它不起作用，它仅适用于 IP 而不适用于主机名.
那么，是否可以通过 Docker 1.10 中的主机名从主机访问 Docker 容器?
更新:
docker-compose.yml
版本:'2'服务:服务_a:图片:nginx容器名称:docker_a端口:- 8080:80服务_b:图片:nginx容器名称:docker_b端口:- 8081:80然后我通过命令启动它:docker-compose up --force-recreate
当我跑步时:
docker exec -i -t docker_a ping -c4 docker_b- 有效docker exec -i -t docker_b ping -c4 docker_a- 有效ping 172.19.0.2- 它可以工作(172.19.0.2是docker_b的 ip)ping docker_a- 失败
docker network inspect test_default 的结果是
As 在这里回答有一个软件解决方案这个，复制答案:
<小时>有一个开源应用程序可以解决这个问题，它叫做 DNS 代理服务器
这是一个解析容器主机名的 DNS 服务器，当它无法解析主机名时，它可以使用公共名称服务器来解析它.
启动 DNS 服务器
$ docker run --hostname dns.mageddo --name dns-proxy-server -p 5380:5380 -v/var/run/docker.sock:/var/run/docker.sock -v/etc/resolv.conf:/etc/resolv.conf defreitas/dns-代理服务器它会自动设置为您的默认 DNS(并在停止时恢复到原始 DNS).
启动容器进行测试
docker-compose updocker-compose.yml
版本:'2'服务:Redis:容器名称:redis图像:redis:2.8主机名:redis.dev.intranetnetwork_mode: bridge # 这样他甚至可以在内部解析其他容器名称，例如解析elasticsearch弹性搜索:容器名称:elasticsearch图片:elasticsearch:2.2主机名:elasticsearch.dev.intranet现在解析容器的主机名
来自主持人
$ nslookup redis.dev.intranet服务器:172.17.0.2地址:172.17.0.2#53非权威回答:名称:redis.dev.intranet地址:172.21.0.3来自另一个容器
$ docker exec -it redis ping elasticsearch.dev.intranetPING elasticsearch.dev.intranet (172.21.0.2):56 个数据字节它还可以解析 Internet 主机名
$ nslookup google.com服务器:172.17.0.2地址:172.17.0.2#53非权威回答:名称:google.com地址:216.58.202.78I have the Docker version 1.10 with embedded DNS service.
I have created two service containers in my docker-compose file. They are reachable each other by hostname and by IP, but when I would like reach one of them from the host machine, it doesn't work, it works only with IP but not with hostname.
So, is it possible to access a docker container from the host machine by it's hostname in the Docker 1.10, please?
Update:
docker-compose.yml
version: '2'
services:
service_a:
image: nginx
container_name: docker_a
ports:
- 8080:80
service_b:
image: nginx
container_name: docker_b
ports:
- 8081:80
then I start it by command: docker-compose up --force-recreate
when I run:
docker exec -i -t docker_a ping -c4 docker_b- it worksdocker exec -i -t docker_b ping -c4 docker_a- it worksping 172.19.0.2- it works (172.19.0.2isdocker_b's ip)ping docker_a- fails
The result of the docker network inspect test_default is
[
{
"Name": "test_default",
"Id": "f6436ef4a2cd4c09ffdee82b0d0b47f96dd5aee3e1bde068376dd26f81e79712",
"Scope": "local",
"Driver": "bridge",
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "172.19.0.0/16",
"Gateway": "172.19.0.1/16"
}
]
},
"Containers": {
"a9f13f023761123115fcb2b454d3fd21666b8e1e0637f134026c44a7a84f1b0b": {
"Name": "docker_a",
"EndpointID": "a5c8e08feda96d0de8f7c6203f2707dd3f9f6c3a64666126055b16a3908fafed",
"MacAddress": "02:42:ac:13:00:03",
"IPv4Address": "172.19.0.3/16",
"IPv6Address": ""
},
"c6532af99f691659b452c1cbf1693731a75cdfab9ea50428d9c99dd09c3e9a40": {
"Name": "docker_b",
"EndpointID": "28a1877a0fdbaeb8d33a290e5a5768edc737d069d23ef9bbcc1d64cfe5fbe312",
"MacAddress": "02:42:ac:13:00:02",
"IPv4Address": "172.19.0.2/16",
"IPv6Address": ""
}
},
"Options": {}
}
]
As answered here there is a software solution for this, copying the answer:
There is an open source application that solves this issue, it's called DNS Proxy Server
It's a DNS server that resolves container hostnames, and when it can't resolve a hostname then it can resolve it using public nameservers.
Start the DNS Server
$ docker run --hostname dns.mageddo --name dns-proxy-server -p 5380:5380
-v /var/run/docker.sock:/var/run/docker.sock
-v /etc/resolv.conf:/etc/resolv.conf
defreitas/dns-proxy-server
It will set as your default DNS automatically (and revert back to the original when it stops).
Start your container for the test
docker-compose up
docker-compose.yml
version: '2'
services:
redis:
container_name: redis
image: redis:2.8
hostname: redis.dev.intranet
network_mode: bridge # that way he can solve others containers names even inside, solve elasticsearch, for example
elasticsearch:
container_name: elasticsearch
image: elasticsearch:2.2
hostname: elasticsearch.dev.intranet
Now resolve your containers' hostnames
from host
$ nslookup redis.dev.intranet
Server: 172.17.0.2
Address: 172.17.0.2#53
Non-authoritative answer:
Name: redis.dev.intranet
Address: 172.21.0.3
from another container
$ docker exec -it redis ping elasticsearch.dev.intranet
PING elasticsearch.dev.intranet (172.21.0.2): 56 data bytes
As well it resolves Internet hostnames
$ nslookup google.com
Server: 172.17.0.2
Address: 172.17.0.2#53
Non-authoritative answer:
Name: google.com
Address: 216.58.202.78
这篇关于Docker 1.10 通过主机名从主机访问容器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
