gpt4 book ai didi

Docker 1.10 通过主机名从主机访问容器

转载 作者:IT老高 更新时间:2023-10-28 12:36:32 28 4
gpt4 key购买 nike

我有带有嵌入式 DNS 服务的 Docker 1.10 版。

我在 docker-compose 文件中创建了两个服务容器。它们可以通过主机名和 IP 相互访问,但是当我想从主机访问其中一个时,它不起作用,它仅适用于 IP,但不适用于主机名。

那么,请问是否可以通过 Docker 1.10 中的主机名从主机访问 docker 容器?

更新:

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

然后我通过命令启动它: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.2docker_b 的 ip)
  • ping docker_a - 失败

docker network inspect test_default的结果是

[
{
"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": {}
}
]

最佳答案

作为 answered here有一个软件解决方案,复制答案:


有一个开源应用程序可以解决这个问题,它被称为 DNS Proxy Server

它是一个解析容器主机名的 DNS 服务器,当它无法解析主机名时,它可以使用公共(public)名称服务器来解析它。

启动 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-proxy-server

它将自动设置为您的默认 DNS(并在停止时恢复为原始 DNS)。

启动你的容器进行测试

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

现在解析容器的主机名

来自主机

$ 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

来自另一个容器

$ docker exec -it redis ping elasticsearch.dev.intranet
PING elasticsearch.dev.intranet (172.21.0.2): 56 data bytes

它还能解析互联网主机名

$ 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 通过主机名从主机访问容器,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/35828487/

28 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com