解决docker启动时报‘Error response from daemon: network xxx not found‘问题

绝地灬酷狼 2023-10-09 21:41 102阅读 0赞

公司近期更换了网络设备,网段也更换了,导致原来的测试服务器无法连接,网关强制重启后才得以解决。
服务器启动后几个docker服务没有正常重启。
执行命令查询服务状态

  1. docker ps -a

确实有几个服务停止运行了,于是手动执行启动命令

  1. docker start nacos

返回异常信息

  1. Error response from daemon: network f0e06a7bb7c48bc5765c576a78fbc918062ebd18ab0c2c5f95a22109f43e4d5b not found

再次查看创建的network信息

  1. docker network ls

得到的结果如下
























NETWORK ID NAME DRIVER SCOPE
f329f40ed61b bridge bridge local
23da4d14f772 host host local

查看网络的具体配置

  1. docker network inspect f329f40ed61b

得到的结果

  1. [
  2. {
  3. "Name": "bridge",
  4. "Id": "f329f40ed61b335f23c0fd079dc341b37945e50046451c89364c431313da0c14",
  5. "Created": "2023-05-06T08:51:16.831699243+08:00",
  6. "Scope": "local",
  7. "Driver": "bridge",
  8. "EnableIPv6": false,
  9. "IPAM": {
  10. "Driver": "default",
  11. "Options": null,
  12. "Config": [
  13. {
  14. "Subnet": "192.168.200.0/24",
  15. "Gateway": "192.168.200.1"
  16. }
  17. ]
  18. },
  19. "Internal": false,
  20. "Attachable": false,
  21. "Ingress": false,
  22. "ConfigFrom": {
  23. "Network": ""
  24. },
  25. "ConfigOnly": false,
  26. "Containers": {
  27. "1004b28c5b7bd7e9e31ed51e3eb11df294bd18ac1d409a7f9ec83e99e4b75c89": {
  28. "Name": "service",
  29. "EndpointID": "004858fd0173d6da107bbd1e8ca1b9281e2ecbd481b5fd93c79e73bfa3aeb669",
  30. "MacAddress": "02:42:c0:a8:c8:07",
  31. "IPv4Address": "192.168.200.7/24",
  32. "IPv6Address": ""
  33. },
  34. ... ... <省略其他配置>

再查看刚才的nacos容器详情

  1. docker inspect nacos

得到的网络配置信息如下

  1. ... ...
  2. "Networks": {
  3. "network": {
  4. "IPAMConfig": {
  5. "IPv4Address": "172.16.0.4"
  6. },
  7. "Links": null,
  8. "Aliases": [
  9. "d3183ca265e9"
  10. ],
  11. "NetworkID": "f0e06a7bb7c48bc5765c576a78fbc918062ebd18ab0c2c5f95a22109f43e4d5b",
  12. "EndpointID": "",
  13. "Gateway": "",
  14. "IPAddress": "",
  15. "IPPrefixLen": 0,
  16. "IPv6Gateway": "",
  17. "GlobalIPv6Address": "",
  18. "GlobalIPv6PrefixLen": 0,
  19. "MacAddress": "",
  20. "DriverOpts": null
  21. }
  22. }

可以看得到两个IP不一样,那就肯定原来nacos所绑定的network被删除了,需要重新创建

  1. docker network create --driver bridge --subnet 172.16.0.0/16 --gateway 172.16.0.1 network

查看创建后的网络信息

  1. docker network list

可以看到已经创建好了,之后需要重新绑定






























NETWORK ID NAME DRIVER SCOPE
f329f40ed61b bridge bridge local
23da4d14f772 host host local
0713e1d89b4b network bridge local

先解绑

  1. docker network disconnect 0713e1d89b4b nacos

再绑定

  1. docker network connect 0713e1d89b4b nacos

再次查看容器的网络信息,正常显示了

  1. "Networks": {
  2. "network": {
  3. "IPAMConfig": {
  4. },
  5. "Links": null,
  6. "Aliases": [
  7. "d3183ca265e9"
  8. ],
  9. "NetworkID": "0713e1d89b4bb63af3c66c98448c5581ec2c5cd32573af71bff16e00fe1a1439",
  10. "EndpointID": "532a01a29124eed661e67ab3cc0e7c3fd772dc584adc1d944757e1be57951c46",
  11. "Gateway": "172.16.0.1",
  12. "IPAddress": "172.16.0.3",
  13. "IPPrefixLen": 16,
  14. "IPv6Gateway": "",
  15. "GlobalIPv6Address": "",
  16. "GlobalIPv6PrefixLen": 0,
  17. "MacAddress": "02:42:ac:10:00:03",
  18. "DriverOpts": {
  19. }
  20. }
  21. }

重新启动服务

  1. docker start nacos

正常启动,剩下的网络也按照这个方法启动成功。

发表评论

表情:
评论列表 (有 0 条评论,102人围观)

还没有评论,来说两句吧...

相关阅读