Docker连接问题: apt/apk在docker容器内和docker构建期间不起作用
Docker连接问题: apt/apk在docker容器内和docker构建期间不起作用
提问于 2019-03-10 00:42:58
两天以来，我一直在为下面的问题而苦苦挣扎。当我尝试运行包管理系统来构建一个新的容器镜像时，它们会失败，我尝试使用alpine:latest和ubuntu:latest。如果我尝试从运行的容器中使用它们，即使我使用--network host选项，也会得到相同的行为。
例如，如果我尝试构建以下容器：
FROM alpine:latest
RUN apk update如下所示：
docker build --no-cache -t test .我得到了：
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.9/main: could not connect to server (check repositories file)
WARNING: Ignoring APKINDEX.b89edf6e.tar.gz: No such file or directory
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.9/community: could not connect to server (check repositories file)
WARNING: Ignoring APKINDEX.737f7e01.tar.gz: No such file or directory使用ubuntu：
FROM ubuntu:latest
RUN apt-get update我得到了：
Sending build context to Docker daemon 3.954MB
Step 1/2 : FROM ubuntu:latest
---> 47b19964fb50
Step 2/2 : RUN apt-get update
---> Running in 4c637396e7be
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Could not connect to 127.0.0.1:3000 (127.0.0.1). - connect (111:Connection refused)
Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Could not connect to 127.0.0.1:3000 (127.0.0.1). - connect (111:Connection refused)
Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Unable to connect to 127.0.0.1:3000:
Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Unable to connect to 127.0.0.1:3000:
Reading package lists...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not connect to 127.0.0.1:3000 (127.0.0.1). - connect (111: Connection refused)
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Unable to connect to 127.0.0.1:3000:
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Unable to connect to 127.0.0.1:3000:
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Could not connect to 127.0.0.1:3000 (127.0.0.1). connect (111: Connection refused)
W: Some index files failed to download. They have been ignored, or old ones used instead.
Removing intermediate container 4c637396e7be
---> e41da39b1a0d
Successfully built e41da39b1a0d
Successfully tagged test:latest我在ubuntu 16.04主机上使用Docker版本18.09.3，build 774a1f4。我的系统在路由器后面运行。我已经尝试了this answer和this answer中建议的策略，但没有任何运气。更奇怪的是，如果我从adiazmor/docker-ubuntu-with-ping执行ping命令，如下所示：
docker run --rm -it adiazmor/docker-ubuntu-with-ping
root@a774331799d3:/# ping google.com
PING google.com (216.58.205.46): 56 data bytes
64 bytes from 216.58.205.46: icmp_seq=0 ttl=53 time=44.976 ms
64 bytes from 216.58.205.46: icmp_seq=1 ttl=53 time=43.661 ms
64 bytes from 216.58.205.46: icmp_seq=2 ttl=53 time=43.471 ms
64 bytes from 216.58.205.46: icmp_seq=3 ttl=53 time=44.066 ms
64 bytes from 216.58.205.46: icmp_seq=4 ttl=53 time=43.849 ms它可以工作，但是apt-get更新像以前一样失败。我的想法快用完了。任何帮助都是非常感谢的。
更新:一些容器似乎能够找到合适的DNS服务器，而其他容器则不能。
实际上，如果我运行：
docker run --rm -i busybox nslookup google.com它不起作用：
Unable to find image 'busybox:latest' locallylatest: Pulling from library/busybox
697743189b6d: Pull complete
Digest: sha256:061ca9704a714ee3e8b80523ec720c64f6209ad3f97c0ff7cb9ec7d19f15149f
Status: Downloaded newer image for busybox:latest
Server: 8.8.8.8
Address: 8.8.8.8:53
Non-authoritative answer:
Name: google.com
Address: 2a00:1450:4002:807::200e
*** Can't find google.com: No answer但是如果我运行：
docker run --rm -it tutum/dnsutils nslookup google.com它是有效的：
Unable to find image 'tutum/dnsutils:latest' locally
latest: Pulling from tutum/dnsutils
a3ed95caeb02: Pull complete
0d4f8675aa34: Pull complete
7cf67d95acf6: Pull complete
56692d2aae61: Pull complete
349ad02ed73a: Pull complete
Digest: sha256:d2244ad47219529f1003bd1513f5c99e71655353a3a63624ea9cb19f8393d5fe
Status: Downloaded newer image for tutum/dnsutils:latest
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: google.com
Address: 216.58.205.78Stack Overflow用户
发布于 2019-03-10 19:13:07
更新:问题的根本原因在于我的本地用户配置(/home/myuser/.docker/config.json)，实际上是它将默认代理设置为127.0.0.1:3000。
好吧，我发现了问题，至少在ubuntu上是这样，它一直在我面前。信不信由你，ubuntu官方镜像中的http_proxy和HTTP_PROXY都设置为127.0.0.1:3000。实际上，我刚刚在我的Dockerfile.ubuntu上测试了这个更改：
FROM ubuntu:latest
RUN echo $HTTP_PROXY && echo $http_proxy && unset HTTP_PROXY && unset http_proxy && apt-get update它工作得很好：
$ docker build --no-cache -f Dockerfile.ubuntu .
Sending build context to Docker daemon 3.956MB
Step 1/2 : FROM ubuntu:latest
---> 47b19964fb50
Step 2/2 : RUN echo $HTTP_PROXY && echo $http_proxy && unset HTTP_PROXY && unset http_proxy && apt-get update
---> Running in bc697aa04846
http://127.0.0.1:3000
http://127.0.0.1:3000
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:4 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [358 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:6 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [3910 B]
Get:7 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [5436 B]
Get:8 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [157 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [10.8 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [946 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [6966 B]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [708 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [3650 B]
Fetched 15.6 MB in 10s (1578 kB/s)
Reading package lists...
Removing intermediate container bc697aa04846
---> 0b6a1f333528
Successfully built 0b6a1f333528在我看来，这似乎违反了隔离原则，但可能有一个很好的原因，我想知道它，有人能解释为什么这两个环境变量是默认设置的吗？
更新：
这个问题在阿尔卑斯山也是一样的。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/55079577
复制相关文章
相似问题
腾讯云开发者
