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的響應時遇到了錯誤??赡艿脑虬ňW(wǎng)絡問題、認證問題、注冊中心URL不正確或者注冊中心服務本身不可用。
2、解決方法
2.1、檢查網(wǎng)絡連接
確保你的機器可以訪問互聯(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服務狀態(tài)
運行systemctl status docker(Linux系統(tǒng))查看Docker服務是否正在運行。
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
重啟服務
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)以下情況,說明問題已解決,如下圖:

總結
到此這篇關于Docker pull時報錯:https://registry-1.docker.io/v2/完美解決辦法的文章就介紹到這了,更多相關Docker pull報錯https://registry-1.docker.io/v2/內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關文章希望大家以后多多支持腳本之家!
- 解決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拉取鏡像報錯問題及解決
相關文章
docker容器中登陸并操作postgresql的實現(xiàn)
本文主要介紹了docker容器中登陸并操作postgresql的實現(xiàn),文中通過示例代碼介紹的非常詳細,對大家的學習或者工作具有一定的參考學習價值,需要的朋友們下面隨著小編來一起學習學習吧2024-02-02
Docker?Push?Skipped?foreign?layer?的錯誤問題及解決方案
當Docker推送基于Windows鏡像到私有倉庫的時候會遇到Skipped foreign layer的問題,這篇文章主要介紹了Docker?Push?Skipped?foreign?layer?的錯誤問題及解決方案,需要的朋友可以參考下2022-05-05
linux中無make命令的問題(make: *** 沒有指明目標并且找不到 makefile及make命令安裝方法)
這篇文章主要介紹了linux中無make命令的問題(make: *** 沒有指明目標并且找不到 makefile及make命令安裝方法),本文給大家介紹的非常詳細,對大家的學習或工作具有一定的參考借鑒價值,需要的朋友可以參考下2020-08-08

