docker报错-无法连接到 Docker Hub 仓库

问题

执行linux命令docker run hello-world,结果报无法连接到docker仓库或者超时的错误,如图

解决

修改docker的仓库镜像源,修改/etc/docker/daemon.json文件。如果在/etc/docker下找不到daemon.json文件,就创建该文件,配置如下

bash 复制代码
{
  #增加registry-mirrors镜像源
  "registry-mirrors": ["https://docker.m.daocloud.io"],
  "insecure-registries" : [
    "docker-registry.zjq.com"
  ],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "10"
  },
  "data-root": "/usr/local/env/rabbitmq/data"
}

再执行systemctl restart docker命令,重新启动docker,然后执行docker info命令,就可以看到docker的镜像源已经被修改成功

bash 复制代码
Client: Docker Engine - Community
 Version:    26.1.3
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 26.1.3
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 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: 8b3b7ca2e5ce38e8f31a34f35b2b68ceb8470d89
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: 4.18.0-147.el8.x86_64
 Operating System: CentOS Linux 8 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 1.764GiB
 Name: localhost.localdomain
 ID: b775db5b-a895-4701-881e-e190b8344ebd
 Docker Root Dir: /usr/local/env/rabbitmq/data
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  docker-registry.zjq.com
  127.0.0.0/8
 Registry Mirrors:
  https://docker.m.daocloud.io/
 Live Restore Enabled: false

重新执行docker run hello-world命令就可以得到如图

bash 复制代码
17eec7bbc9d7: Pull complete 
Digest: sha256:f7931603f70e13dbd844253370742c4fc4202d290c80442b2e68706d8f33ce26
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/
相关推荐
saber_andlibert1 天前
【docker】 镜像的制作——主从数据库创建
数据库·docker·容器
永不停歇的蜗牛1 天前
Linux离线安装Docker最简单的方法
linux·docker·eureka
飞舞花下1 天前
通过本地虚拟机K8S部署项目实践
云原生·容器·kubernetes
ChrisitineTX1 天前
K8s 环境下的 Java 诡异停顿:CPU 没满,为什么 Pod 被 CFS Quota 限制得动弹不得?
java·容器·kubernetes
海鸥811 天前
Descheduler for Kubernetes
云原生·容器·kubernetes
新手小白*1 天前
K8S-RBAC 认证中心
云原生·容器·kubernetes
永不停歇的蜗牛1 天前
K8S之Service和Pod的关系(二)
云原生·容器·kubernetes
基哥的奋斗历程1 天前
部署指南-1A-单体Docker-阿里云方案
阿里云·docker·容器
基哥的奋斗历程1 天前
部署指南-2B-集群K8s-自建方案
云原生·容器·kubernetes