Docker pull報(bào)錯(cuò):https://registry-1.docker.io/v2/的解決方法
1、錯(cuò)誤描述
root@ubuntu-database:/opt/dify/docker# docker compose up -d
[+] Running 9/9
? api Error context canceled 15.1s
? db Error context canceled 15.1s
? nginx Error context canceled 15.1s
? redis Error Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 15.1s
? ssrf_proxy Error context canceled 15.1s
? worker Error context canceled 15.1s
? weaviate Error context canceled 15.1s
? sandbox Error context canceled 15.1s
? web Error context canceled 15.1s
Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
這個(gè)錯(cuò)誤表明Docker客戶端嘗試訪問(wèn)Docker Hub或其他Docker注冊(cè)中心時(shí)出現(xiàn)了問(wèn)題。具體來(lái)說(shuō),是在嘗試獲取注冊(cè)中心API的響應(yīng)時(shí)遇到了錯(cuò)誤??赡艿脑虬ňW(wǎng)絡(luò)問(wèn)題、認(rèn)證問(wèn)題、注冊(cè)中心URL不正確或者注冊(cè)中心服務(wù)本身不可用。
2、解決方法
2.1、檢查網(wǎng)絡(luò)連接
root@ubuntu-database:/opt/dify/docker# ping www.baidu.com PING www.a.shifen.com (110.242.68.3) 56(84) bytes of data. 64 bytes from 110.242.68.3: icmp_seq=1 ttl=128 time=38.5 ms 64 bytes from 110.242.68.3: icmp_seq=2 ttl=128 time=36.4 ms 64 bytes from 110.242.68.3: icmp_seq=3 ttl=128 time=52.3 ms
2.2、檢查Docker服務(wù)狀態(tài)
運(yùn)行systemctl status docker(Linux系統(tǒng))查看Docker服務(wù)是否正在運(yùn)行。
root@ubuntu-database:/opt/dify/docker# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-11-27 12:04:05 UTC; 55min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 4766 (dockerd)
Tasks: 10
Memory: 21.8M (peak: 24.5M)
CPU: 479ms
CGroup: /system.slice/docker.service如以上都沒(méi)有問(wèn)題,下面考慮docker換源
2.3、換源
sudo mkdir -p /etc/docker vim /etc/docker/daemon.json
首先進(jìn)入/etc/docker/daemon.json文件
然后在里面加入下面的配置
{
"registry-mirrors" : ["https://docker.registry.cyou",
"https://docker-cf.registry.cyou",
"https://dockercf.jsdelivr.fyi",
"https://docker.jsdelivr.fyi",
"https://dockertest.jsdelivr.fyi",
"https://mirror.aliyuncs.com",
"https://dockerproxy.com",
"https://mirror.baidubce.com",
"https://docker.m.daocloud.io",
"https://docker.nju.edu.cn",
"https://docker.mirrors.sjtug.sjtu.edu.cn",
"https://docker.mirrors.ustc.edu.cn",
"https://mirror.iscas.ac.cn",
"https://docker.rainbond.cc",
"https://do.nark.eu.org",
"https://dc.j8.work",
"https://dockerproxy.com",
"https://gst6rzl9.mirror.aliyuncs.com",
"https://registry.docker-cn.com",
"http://hub-mirror.c.163.com",
"http://mirrors.ustc.edu.cn/",
"https://mirrors.tuna.tsinghua.edu.cn/",
"http://mirrors.sohu.com/"
],
"insecure-registries" : [
"registry.docker-cn.com",
"docker.mirrors.ustc.edu.cn"
],
"debug": true,
"experimental": false
}重載生效
sudo systemctl daemon-reload
重啟服務(wù)
sudo systemctl restart docker
查看是否配置成功
docker info
root@ubuntu-database:/etc/docker# docker info
Client: Docker Engine - Community
Version: 27.3.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.17.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.7
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 27.3.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 57f17b0a6295a39009d861b89e3b3b87b005ca27
runc version: v1.1.14-0-g2c9f560
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-49-generic
Operating System: Ubuntu 24.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.709GiB
Name: ubuntu-database
ID: acb5a888-7140-4e43-8924-6fc325481944
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 23
Goroutines: 40
System Time: 2024-11-27T13:09:10.861401847Z
EventsListeners: 0
Experimental: false
Insecure Registries:
docker.mirrors.ustc.edu.cn
registry.docker-cn.com
127.0.0.0/8
Registry Mirrors:
https://docker.registry.cyou/
https://docker-cf.registry.cyou/
https://dockercf.jsdelivr.fyi/
https://docker.jsdelivr.fyi/
https://dockertest.jsdelivr.fyi/
https://mirror.aliyuncs.com/
https://dockerproxy.com/
https://mirror.baidubce.com/
https://docker.m.daocloud.io/
https://docker.nju.edu.cn/
https://docker.mirrors.sjtug.sjtu.edu.cn/
https://docker.mirrors.ustc.edu.cn/
https://mirror.iscas.ac.cn/
https://docker.rainbond.cc/
https://do.nark.eu.org/
https://dc.j8.work/
https://gst6rzl9.mirror.aliyuncs.com/
https://registry.docker-cn.com/
http://hub-mirror.c.163.com/
http://mirrors.ustc.edu.cn/
https://mirrors.tuna.tsinghua.edu.cn/
http://mirrors.sohu.com/
Live Restore Enabled: false
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

重新執(zhí)行 :docker compose up -d
出現(xiàn)以下情況,說(shuō)明問(wèn)題已解決,如下圖:

到此這篇關(guān)于Docker pull報(bào)錯(cuò):https://registry-1.docker.io/v2/的解決方法的文章就介紹到這了,更多相關(guān)Docker pull報(bào)錯(cuò)解決內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
- 解決docker?pull出現(xiàn)錯(cuò)誤:Error?response?from?daemon
- docker?pull出現(xiàn)錯(cuò)誤或速度慢具體解決辦法
- 解決docker pull鏡像報(bào)錯(cuò)的問(wèn)題
- 解決Docker pull拉取鏡像報(bào)錯(cuò)“Error response from daemon:Get“https://registry-1.docker.io/v2”問(wèn)題
- Docker拉鏡像報(bào)錯(cuò)error pulling image configuration: unknown blob
- docker?pull?mysql報(bào)missing?signature?key錯(cuò)誤解決辦法
- docker?pull拉取鏡像報(bào)錯(cuò)問(wèn)題及解決
- Docker?pull時(shí)報(bào)錯(cuò):https://registry-1.docker.io/v2/完美解決辦法
相關(guān)文章
docker容器中無(wú)法獲取宿主機(jī)hostname的解決方案
這篇文章主要介紹了docker容器中無(wú)法獲取宿主機(jī)hostname的解決方案,具有很好的參考價(jià)值,希望對(duì)大家有所幫助。一起跟隨小編過(guò)來(lái)看看吧2021-03-03
Docker容器中Kingbase數(shù)據(jù)庫(kù)授權(quán)到期更換的解決方案
當(dāng)Docker容器內(nèi)的Kingbase數(shù)據(jù)庫(kù)授權(quán)文件(license.dat)到期后,會(huì)直接導(dǎo)致數(shù)據(jù)庫(kù)無(wú)法啟動(dòng)、核心功能受限,本文結(jié)合官方鏡像特性與實(shí)操經(jīng)驗(yàn),整理了一套完整、可直接落地的授權(quán)更換與數(shù)據(jù)庫(kù)恢復(fù)方案,需要的朋友可以參考下2026-04-04
Docker中的容器網(wǎng)絡(luò)和通信原理詳解
這篇文章主要介紹了Docker中的容器網(wǎng)絡(luò)和通信原理,具有很好的參考價(jià)值,希望對(duì)大家有所幫助,如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2025-04-04
excel導(dǎo)出在docker環(huán)境中總是失敗的問(wèn)題
這篇文章主要介紹了excel導(dǎo)出在docker環(huán)境中總是失敗的問(wèn)題及解決方法,本文給大家介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或工作具有一定的參考借鑒價(jià)值,2020-09-09
5分鐘教你實(shí)現(xiàn)用docker搭建Redis集群模式和哨兵模式
本文主要介紹了5分鐘實(shí)現(xiàn)用docker搭建Redis集群模式和哨兵模式,文中通過(guò)示例代碼介紹的非常詳細(xì),具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2021-09-09
Docker出現(xiàn)tag顯示none鏡像的處理方案
本文介紹了Docker中出現(xiàn)REPOSITORY和TAG都顯示為<none>的鏡像,即懸掛鏡像的原因,并提供了解決方法,包括查找和刪除懸掛鏡像,以及為它們指定新的標(biāo)簽2025-02-02
使用docker容器來(lái)構(gòu)建前端項(xiàng)目過(guò)程
文章介紹了如何使用Docker容器來(lái)解決前端項(xiàng)目打包問(wèn)題,包括構(gòu)建鏡像、設(shè)置環(huán)境變量、加速構(gòu)建過(guò)程以及如何將node_modules直接打包到鏡像中,通過(guò)這種方式,可以確保每次打包的環(huán)境一致,避免因環(huán)境差異導(dǎo)致的打包失敗2026-03-03
使用Docker部署Jenkins并實(shí)現(xiàn)自動(dòng)化部署的全流程
本文介紹了使用Docker部署Jenkins并實(shí)現(xiàn)自動(dòng)化部署的完整路徑,涵蓋Docker環(huán)境準(zhǔn)備與選擇、Jenkins容器部署與權(quán)限設(shè)置、DockerSocket與Docker-in-Docker兩種方案對(duì)比、Jenkins初始化與插件配置、憑證管理、Jenkinsfile自動(dòng)化部署流水線、多分支流水線配置等等內(nèi)容2026-05-05

