docker报错
centos7安装docker以后右上角有线连接哪里出现了好多有线连接，该怎末办
在CentOS 7安装Docker后，右上角网络连接区域出现多个有线连接的情况，可能是由于Docker创建网络接口或者系统网络配置受影响导致的。以下是一些可能的解决办法：
1. 理解Docker网络接口
Docker在安装和运行过程中会创建一些网络接口，像 docker0 是默认的桥接网络接口，还有可能会根据不同的网络模式创建其他虚拟网络接口。这些接口一般不会影响正常的网络连接，不过可能会在网络管理工具里显示出来。
2. 隐藏或删除不必要的网络连接
NetworkManager 图形界面
- 点击右上角的网络图标，找到那些不需要显示的有线连接。
- 通常可以在连接列表中右键点击该连接，选择“断开连接”或者“隐藏”选项。
命令行方式
[root@192 ~]# docker network
Usage: docker network COMMAND
Manage networks
Commands:
connect Connect a container to a network
create Create a network
disconnect Disconnect a container from a network
inspect Display detailed information on one or more networks
ls List networks
prune Remove all unused networks
rm Remove one or more networks
Run 'docker network COMMAND --help' for more information on a command.
[root@192 ~]# nmcli connection show # 查看所有的网络连接
名称 UUID 类型 设备
docker0 42d8b1f0-93ad-49c6-a9ec-5cdb7a82165a bridge docker0
virbr0 3466d071-f191-48f4-ad8a-f3c1fc671a4e bridge virbr0
有线连接 10 2211d3aa-1f04-4c59-aacc-f74804fb6b91 802-3-ethernet ens33
ens33 bd33bf11-fc29-4421-8725-6c1eb002de9b 802-3-ethernet --
有线连接 1 88836db3-c45e-49f0-a5d4-ccd46dd3f126 802-3-ethernet --
有线连接 2 6f75954d-db35-41cf-9002-67c6434cb7fb 802-3-ethernet --
有线连接 3 d7cd731f-7e00-4e1e-a4be-49d30f0af00a 802-3-ethernet --
有线连接 4 e131f29e-6ceb-48da-9543-2a32b8adc654 802-3-ethernet --
有线连接 5 1eaf36aa-48ed-44f6-a69d-c5873f414418 802-3-ethernet --
有线连接 6 a4a591b5-bbca-4220-bfc7-c4ff3e178e02 802-3-ethernet --
有线连接 7 6652ab71-2d9b-4a80-8c6e-57bc3de6b950 802-3-ethernet --
有线连接 8 bdf712b0-b88f-473c-8d43-2375cd02eac3 802-3-ethernet --
有线连接 9 1314c5e1-0c32-4a4d-a85b-c5436e132623 802-3-ethernet --
[root@192 ~]# nmcli connection delete 88836db3-c45e-49f0-a5d4-ccd46dd3f126 # 删除多余的连接名称
成功删除连接 '有线连接 1'（88836db3-c45e-49f0-a5d4-ccd46dd3f126）。
[root@192 ~]# nmcli connection delete 6f75954d-db35-41cf-9002-67c6434cb7fb
成功删除连接 '有线连接 2'（6f75954d-db35-41cf-9002-67c6434cb7fb）。
[root@192 ~]# nmcli connection delete d7cd731f-7e00-4e1e-a4be-49d30f0af00a
成功删除连接 '有线连接 3'（d7cd731f-7e00-4e1e-a4be-49d30f0af00a）。
[root@192 ~]# nmcli connection delete e131f29e-6ceb-48da-9543-2a32b8adc654
成功删除连接 '有线连接 4'（e131f29e-6ceb-48da-9543-2a32b8adc654）。
[root@192 ~]# nmcli connection delete 1eaf36aa-48ed-44f6-a69d-c5873f414418
成功删除连接 '有线连接 5'（1eaf36aa-48ed-44f6-a69d-c5873f414418）。
[root@192 ~]# nmcli connection delete a4a591b5-bbca-4220-bfc7-c4ff3e178e02
成功删除连接 '有线连接 6'（a4a591b5-bbca-4220-bfc7-c4ff3e178e02）。
[root@192 ~]# nmcli connection delete 6652ab71-2d9b-4a80-8c6e-57bc3de6b950
成功删除连接 '有线连接 7'（6652ab71-2d9b-4a80-8c6e-57bc3de6b950）。
[root@192 ~]# nmcli connection delete bdf712b0-b88f-473c-8d43-2375cd02eac3
成功删除连接 '有线连接 8'（bdf712b0-b88f-473c-8d43-2375cd02eac3）。
[root@192 ~]# nmcli connection delete 1314c5e1-0c32-4a4d-a85b-c5436e132623
成功删除连接 '有线连接 9'（1314c5e1-0c32-4a4d-a85b-c5436e132623）。
[root@192 ~]# nmcli connection delete 2211d3aa-1f04-4c59-aacc-f74804fb6b91
成功删除连接 '有线连接 10'（2211d3aa-1f04-4c59-aacc-f74804fb6b91）。
[root@192 ~]# ifconfig
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
inet6 fe80::42:eaff:fef4:2b67 prefixlen 64 scopeid 0x20<link>
ether 02:42:ea:f4:2b:67 txqueuelen 0 (Ethernet)
RX packets 11 bytes 940 (940.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 32 bytes 4452 (4.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.27.140 netmask 255.255.255.0 broadcast 192.168.27.255
inet6 fe80::5aab:ace4:a252:e95b prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:89:90:f3 txqueuelen 1000 (Ethernet)
RX packets 150 bytes 16650 (16.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 154 bytes 22286 (21.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 64 bytes 5568 (5.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64 bytes 5568 (5.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vethad220e3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::3097:abff:fee4:f35f prefixlen 64 scopeid 0x20<link>
ether 32:97:ab:e4:f3:5f txqueuelen 0 (Ethernet)
RX packets 11 bytes 1094 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40 bytes 5100 (4.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:5c:57:8b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@192 ~]# nmcli connection show
名称 UUID 类型 设备
docker0 42d8b1f0-93ad-49c6-a9ec-5cdb7a82165a bridge docker0
ens33 bd33bf11-fc29-4421-8725-6c1eb002de9b 802-3-ethernet ens33
virbr0 3466d071-f191-48f4-ad8a-f3c1fc671a4e bridge virbr0
[root@192 ~]# systemctl restart docker # 重启 Docker 服务，让其重新加载网络配置
[root@192 ~]# systemctl restart NetworkManager # 重启 NetworkManager 服务
[root@192 ~]# reboot
Last login: Wed Feb 26 22:32:17 2025 from 192.168.27.1
3. 检查系统日志
查看系统日志文件 /var/log/messages 或者 /var/log/syslog，看是否有与网络连接或者 Docker 相关的错误信息，根据这些信息进一步排查问题。例如，使用以下命令查看最近的日志：
tail -n 50 /var/log/messages
常用容器
部署MySQL
docker pull mysql:5.7
[root@localhost local]# docker run -di --name=mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=root mysql:5.7
[root@localhost local]# docker exec -it mysql /bin/bash
root@c0c4495a4058:/# mysql -uroot -proot --default-character-set=utf8
部署nginx
docker pull nginx
[root@localhost local]# docker run -di --name=nginx -p 80:80 nginx
docker cp nginx:/etc/nginx /usr/local/mydata/nginx/
cd /usr/local/mydata
ll
mv nginx conf
docker stop nginx
docker rm nginx
[root@localhost local]# docker run -di --name=nginx -p 80:80 -v /usr/local/mydata/conf/:/etc/nginx nginx
redis部署
docker pull redis
[root@localhost local]# docker run -di --name=redis -p 6379:6379 redis
部署rabbitmq
docker pull rabbitmq:3.7.12
[root@localhost local]# docker run -di --name=rabbitmq -p 5671:5671 -p 5672:5672 -p 4369:4369 -p 25672:25672 -p 15671:15671 -p 15672:15672 rabbitmq:3.7.12
[root@localhost local]# docker exec -it rabbitmq /bin/bash
root@c0c4495a4058:/# rabbitmq-plugins enable rabbitmq_management
部署zookeeper
Docker镜像pull不下来
[root@192 docker]# docker compose up -d # 安装dify的时候报错
[+] Running 4/4
✘ db Error context canceled 261.7s
✘ web Error context canceled 261.7s
✘ api Error context canceled 261.7s
✘ worker Error Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for conn... 261.7s
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
[root@192 docker]#
[root@192 ~]# journalctl -u docker.service -f # 实时查看 Docker 日志
-- Logs begin at 五 2025-02-21 00:56:48 CST. --
2月 21 01:31:28 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:28.910908410+08:00" level=info msg="Attempting next endpoint for pull after error: manifest unknown: manifest unknown" spanID=5c59b7e7cedd51e0 traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:31 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:31.234749309+08:00" level=info msg="Attempting next endpoint for pull after error: manifest unknown: manifest unknown" spanID=c6d7431183428acf traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:35 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:35.712259792+08:00" level=info msg="Attempting next endpoint for pull after error: manifest unknown: manifest unknown" spanID=c6d7431183428acf traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:36 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:36.691077743+08:00" level=info msg="Attempting next endpoint for pull after error: manifest unknown: manifest unknown" spanID=5c59b7e7cedd51e0 traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:46 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:46.117654443+08:00" level=info msg="Attempting next endpoint for pull after error: manifest unknown: manifest unknown" spanID=5c59b7e7cedd51e0 traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:50 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:50.713115331+08:00" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" spanID=c6d7431183428acf traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:50 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:50.713180746+08:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" spanID=c6d7431183428acf traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:50 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:50.714118115+08:00" level=error msg="Handler for POST /v1.45/images/create returned error: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" spanID=c6d7431183428acf traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:50 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:50.771935231+08:00" level=error msg="Not continuing with pull after error: manifest unknown: manifest unknown" spanID=5c59b7e7cedd51e0 traceID=578c3895410228f068cc66ff55ce0c8a
2月 21 01:31:50 192.168.27.140 dockerd[7819]: time="2025-02-21T01:31:50.772062172+08:00" level=error msg="Handler for POST /v1.45/images/create returned error: manifest unknown: manifest unknown" spanID=5c59b7e7cedd51e0 traceID=578c3895410228f068cc66ff55ce0c8a
浙公网安备 33010602011771号