Docker?pull時報錯:https://registry-1.docker.io/v2/完美解決辦法
1、錯誤描述
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)
Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
這個錯誤表明Docker客戶端嘗試訪問Docker Hub或其他Docker注冊中心時出現(xiàn)了問題。具體來說,是在嘗試獲取注冊中心API的響應(yīng)時遇到了錯誤??赡艿脑虬ňW(wǎng)絡(luò)問題、認(rèn)證問題、注冊中心URL不正確或者注冊中心服務(wù)本身不可用。
2、解決方法
2.1、檢查網(wǎng)絡(luò)連接
確保你的機器可以訪問互聯(lián)網(wǎng),特別是Docker Hub或你所使用的私有注冊中心。
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)
運行systemctl status docker(Linux系統(tǒng))查看Docker服務(wù)是否正在運行。
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如以上都沒有問題,下面考慮docker換源
2.3、換源
sudo mkdir -p /etc/docker vim /etc/docker/daemon.json
首先進入/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)以下情況,說明問題已解決,如下圖:

總結(jié)
到此這篇關(guān)于Docker pull時報錯:https://registry-1.docker.io/v2/完美解決辦法的文章就介紹到這了,更多相關(guān)Docker pull報錯https://registry-1.docker.io/v2/內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
- 解決docker?pull出現(xiàn)錯誤:Error?response?from?daemon
- docker?pull出現(xiàn)錯誤或速度慢具體解決辦法
- 解決docker pull鏡像報錯的問題
- Docker pull報錯:https://registry-1.docker.io/v2/的解決方法
- 解決Docker pull拉取鏡像報錯“Error response from daemon:Get“https://registry-1.docker.io/v2”問題
- Docker拉鏡像報錯error pulling image configuration: unknown blob
- docker?pull?mysql報missing?signature?key錯誤解決辦法
- docker?pull拉取鏡像報錯問題及解決
相關(guān)文章
Docker使用root用戶進入容器的幾種方法小結(jié)
很多時候,拉取運行的容器,進入時,是非root賬戶,也不知道當(dāng)前賬戶的用戶密碼,甚至無賬戶,但在使用docker時,有時候需要以root用戶權(quán)限進入容器進行操作,所以本文介紹了Docker使用root用戶進入容器的幾種方法,需要的朋友可以參考下2025-09-09
Docker consul的容器服務(wù)更新與發(fā)現(xiàn)的問題小結(jié)
這篇文章主要介紹了Docker consul的容器服務(wù)更新與發(fā)現(xiàn),講解了服務(wù)注冊與發(fā)現(xiàn)的基本概念講解,本文給大家介紹的非常詳細,需要的朋友可以參考下2021-08-08
刪除docker中沒有被使用的數(shù)據(jù)卷volume
發(fā)現(xiàn)docker占用宿主機的磁盤空間很大,這個時候如何來釋放這些數(shù)據(jù)卷占用的空間呢,通過執(zhí)行相關(guān)命令即可順利解決,下面小編給大家介紹下刪除docker中沒有被使用的數(shù)據(jù)卷volume,感興趣的朋友跟隨小編一起看看吧2023-01-01
Mac下Docker Desktop starting的問題及解決過程
作者遇到DockerDesktop啟動卡住的問題,原因是VirtualDiskLimit默認(rèn)64GB限制導(dǎo)致Docker.raw過大,通過復(fù)制Docker.raw、修改文件名、重啟DockerDesktop,然后增加VirtualDiskLimit值并重命名,解決了問題2026-04-04
docker完整配置nginx+php+mysql的方法步驟
這篇文章主要介紹了docker完整配置nginx+php+mysql的方法步驟,小編覺得挺不錯的,現(xiàn)在分享給大家,也給大家做個參考。一起跟隨小編過來看看吧2019-02-02
SkyWalking使用和Docker環(huán)境下部署方式
Skywalking是一款分布式系統(tǒng)的應(yīng)用程序性能監(jiān)視工具,專為微服務(wù)、云原生架構(gòu)和基于容器(Docker、K8S、Mesos)架構(gòu)而設(shè)計,該框架采用字節(jié)碼注入的方式實現(xiàn)代碼的無侵入,數(shù)據(jù)存儲支持Mysql、Elasticsearch等2026-02-02

