docker解析DNS失敗問(wèn)題
更新時(shí)間：2025年04月10日 08:35:20 作者：DeepClick
這篇文章主要介紹了docker解析DNS失敗問(wèn)題,具有很好的參考價(jià)值,希望對(duì)大家有所幫助,如有錯(cuò)誤或未考慮完全的地方,望不吝賜教
問(wèn)題現(xiàn)象
我之前在docker里部署的容器，今天突然訪問(wèn)不了了，一開(kāi)始我以為是容器的問(wèn)題，將容器restart，銷毀重建，都沒(méi)有解決。
最后準(zhǔn)備重啟docker service，在重啟之前，看了一眼docker的狀態(tài)：
ck94 ~]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2023-04-25 10:06:23 CST; 1 months 3 days ago
Docs: https://docs.docker.com
Main PID: 2615 (dockerd)
Tasks: 172
Memory: 8.3G
CGroup: /system.slice/docker.service
├─ 2615 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
├─ 5610 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 55433 -container-ip 172.17.0.3 -container-port 5432
├─ 5627 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 55433 -container-ip 172.17.0.3 -container-port 5432
├─ 5671 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 3000 -container-ip 172.17.0.4 -container-port 3000
├─ 5698 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 3000 -container-ip 172.17.0.4 -container-port 3000
├─21981 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9200 -container-ip 172.20.0.2 -container-port 9200
├─21994 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9200 -container-ip 172.20.0.2 -container-port 9200
├─23558 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 10086 -container-ip 172.20.0.3 -container-port 9000
├─23575 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 10086 -container-ip 172.20.0.3 -container-port 9000
├─23624 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 38080 -container-ip 172.20.0.4 -container-port 8080
├─23640 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 38080 -container-ip 172.20.0.4 -container-port 8080
├─26535 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 49001 -container-ip 172.17.0.2 -container-port 9001
├─26552 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 49001 -container-ip 172.17.0.2 -container-port 9001
├─26602 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 49000 -container-ip 172.17.0.2 -container-port 9000
├─26620 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 49000 -container-ip 172.17.0.2 -container-port 9000
├─39170 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 5601 -container-ip 172.20.0.5 -container-port 5601
└─39182 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 5601 -container-ip 172.20.0.5 -container-port 5601
May 29 09:24:38 ck94 dockerd[2615]: time="2023-05-29T09:24:38.161269040+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:26:22 ck94 dockerd[2615]: time="2023-05-29T09:26:22.679628216+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:26:27 ck94 dockerd[2615]: time="2023-05-29T09:26:27.683446445+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:27:38 ck94 dockerd[2615]: time="2023-05-29T09:27:38.328922576+08:00" level=warning msg="ShouldRestart failed, container will not be restarted" container=4af5eb860cbfea8961372e...
May 29 09:34:18 ck94 dockerd[2615]: time="2023-05-29T09:34:18.236630475+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:35:02 ck94 dockerd[2615]: time="2023-05-29T09:35:02.949012103+08:00" level=warning msg="ShouldRestart failed, container will not be restarted" container=9969a986040d0f91bc80d9...
May 29 09:36:23 ck94 dockerd[2615]: time="2023-05-29T09:36:23.261658623+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:37:48 ck94 dockerd[2615]: time="2023-05-29T09:37:48.429139761+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:39:50 ck94 dockerd[2615]: time="2023-05-29T09:39:50.051518136+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
May 29 09:43:18 ck94 dockerd[2615]: time="2023-05-29T09:43:18.733473159+08:00" level=warning msg="[resolver] failed to read from DNS server: 223.6.6.6:53, query: ;elasticse... i/o timeout"
Hint: Some lines were ellipsized, use -l to show in full.里面報(bào)大量的DNS解析錯(cuò)誤。
我嘗試在不同機(jī)器上curl該容器的url，在本機(jī)執(zhí)行：
ck94 ~]# curl http://192.168.101.94:49001/browser <!doctype html><html lang="en"><head><meta charset="utf-8"/><base href="/" rel="external nofollow" /><meta content="width=device-width,initial-scale=1" name="viewport"/><meta content="#081C42" media="(prefers-color-scheme: light)" name="theme-color"/><meta content="#081C42" media="(prefers-color-scheme: dark)" name="theme-color"/><meta content="MinIO Console" name="description"/><meta name="minio-license" content="agpl" /><link href="./styles/root-styles.css" rel="external nofollow" rel="stylesheet"/><link href="./apple-icon-180x180.png" rel="external nofollow" rel="apple-touch-icon" sizes="180x180"/><link href="./favicon-32x32.png" rel="external nofollow" rel="icon" sizes="32x32" type="image/png"/><link href="./favicon-96x96.png" rel="external nofollow" rel="icon" sizes="96x96" type="image/png"/><link href="./favicon-16x16.png" rel="external nofollow" rel="icon" sizes="16x16" type="image/png"/><link href="./manifest.json" rel="external nofollow" rel="manifest"/><link color="#3a4e54" href="./safari-pinned-tab.svg" rel="external nofollow" rel="mask-icon"/><title>MinIO Console</title><script defer="defer" src="./static/js/main.5efdfa93.js"></script><link href="./static/css/main.57e739f5.css" rel="external nofollow" rel="stylesheet"></head><body><noscript>You need to enable JavaScript to run this app.</noscript><div id="root"><div id="preload"><img src="./images/background.svg"/> <img src="./images/background-wave-orig2.svg"/></div><div id="loader-block"><img src="./Loader.svg"/></div></div></body></html>
是沒(méi)有問(wèn)題的。
我在其他機(jī)器上執(zhí)行：
chenyanchang@chenyanchangdeMacBook-Pro ~ % curl http://192.168.101.94:49001/browser curl: (7) Failed to connect to 192.168.101.94 port 49001: Operation timed out
解決方案
重啟docker服務(wù)，重啟docker0網(wǎng)卡：
service docker stop ip link set dev docker0 down ip link set dev docker0 up service docker start
再次查看， 問(wèn)題解決：
總結(jié)
以上為個(gè)人經(jīng)驗(yàn)，希望能給大家一個(gè)參考，也希望大家多多支持腳本之家。
相關(guān)文章
Docker實(shí)戰(zhàn)指南之MySQL、Redis與C++環(huán)境的深度容器化部署
項(xiàng)目開(kāi)發(fā)中最常用的就是MySQL和Redis了,咱們的實(shí)戰(zhàn)項(xiàng)目的需求開(kāi)發(fā)過(guò)程中也依賴這兩個(gè)基礎(chǔ)環(huán)境,這篇文章主要介紹了Docker實(shí)戰(zhàn)指南之MySQL、Redis與C++環(huán)境的深度容器化部署,需要的朋友可以參考下2025-12-12
詳解Centos7 下建立 Docker 橋接網(wǎng)絡(luò)
本篇文章主要介紹了詳解Centos7 下建立 Docker 橋接網(wǎng)絡(luò)，小編覺(jué)得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過(guò)來(lái)看看吧2017-01-01
這篇文章主要介紹了docker-compose如何安裝skywalking問(wèn)題,2024-01-01
Docker在CentOS7下不能下載鏡像timeout的解決辦法(圖解)
本文給大家記錄下Docker在CentOS7下不能下載鏡像timeout問(wèn)題的解決方法，非常不錯(cuò)，具有參考借鑒價(jià)值，感興趣的朋友一起看看吧2016-11-11
解決執(zhí)行docker daemon命令時(shí)出錯(cuò)的問(wèn)題
daemon 這是docker 操作中十分常用的命令指定項(xiàng)，最近在運(yùn)行docker daemon命令卻發(fā)生了錯(cuò)誤，后來(lái)通過(guò)測(cè)試各種方法終于解決了，現(xiàn)在將方法分享給大家，有需要的朋友們可以參考借鑒，下面來(lái)一起看看吧。2016-11-11
這篇文章主要介紹了Docker容器時(shí)區(qū)調(diào)整操作，具有很好的參考價(jià)值，希望對(duì)大家有所幫助。一起跟隨小編過(guò)來(lái)看看吧2020-11-11
這篇文章主要介紹了docker容器掛載宿主主機(jī)目錄的操作方法,本文給大家介紹的非常詳細(xì)，具有參考借鑒價(jià)值，需要的朋友參考下吧2018-01-01
docker空間爆滿導(dǎo)致的進(jìn)入容器失敗的解決方案
這篇文章主要介紹了docker空間爆滿導(dǎo)致的進(jìn)入容器失敗的解決方案，具有很好的參考價(jià)值，希望對(duì)大家有所幫助。一起跟隨小編過(guò)來(lái)看看吧2021-03-03
Docker 中快速安裝tensorflow環(huán)境的方法步驟
這篇文章主要介紹了Docker 中快速安裝tensorflow環(huán)境的方法步驟，小編覺(jué)得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過(guò)來(lái)看看吧2018-10-10
詳解Windows下運(yùn)用Docker部署Node.js開(kāi)發(fā)環(huán)境
這篇文章主要介紹了詳解Windows下運(yùn)用Docker部署Node.js開(kāi)發(fā)環(huán)境,小編覺(jué)得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過(guò)來(lái)看看吧2017-01-01