docker 在 raspberry pi 4 raspbian buster 上安装后无法访问网络

Question

问题： 我以前在我的树莓派 4 上通过以太网和无线网络工作。

我安装了 Docker 并通过 curl https://raw.githubusercontent.com/reportportal/reportportal/master/docker-compose.yml -o docker-compose.yml 构建了报告门户图像。此安装已成功完成，但有些图像有问题，重新启动后我现在无法访问互联网。

我原以为 docker-compose 使用默认的隔离网络，我知道这是默认行为，但也许这不是真的，或者我缺少其他一些配置步骤。我不是网络专家，所以有点卡在这上面。

这是来自的输出：

跟踪路由 4.4.4.4

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
connect: Network is unreachable

ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether dc:a6:32:04:2a:9c brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether dc:a6:32:04:2a:9d brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:fb:5c:18:31 brd ff:ff:ff:ff:ff:ff
5: br-97a0c2dc3c6b: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:f6:24:06:50 brd ff:ff:ff:ff:ff:ff
21: veth0d17bc0@if20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-97a0c2dc3c6b state UP mode DEFAULT group default 
    link/ether e6:a5:76:1f:2a:40 brd ff:ff:ff:ff:ff:ff link-netnsid 10
23: vethf4fa3c3@if22: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-97a0c2dc3c6b state UP mode DEFAULT group default 
    link/ether be:54:91:32:d6:34 brd ff:ff:ff:ff:ff:ff link-netnsid 5
27: veth05f2b7e@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-97a0c2dc3c6b state UP mode DEFAULT group default 
    link/ether f6:80:67:18:6e:96 brd ff:ff:ff:ff:ff:ff link-netnsid 7
845: vethfcc425d@if844: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-97a0c2dc3c6b state UP mode DEFAULT group default 
    link/ether 8a:bc:ad:0e:ed:67 brd ff:ff:ff:ff:ff:ff link-netnsid 0

ifconfig

br-97a0c2dc3c6b: flags=4163 mtu 1500 inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255 inet6 fe80::42:f6ff:fe24:650 prefixlen 64 scopeid 0x20 ether 02:42:f6:24:06:50 txqueuelen 0 (Ethernet) RX packets 56 bytes 7101 (6.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 6760 (6.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099 mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:fb:5c:18:31 txqueuelen 0 (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

eth0: flags=4163 mtu 1500 inet6 fe80::48ed:6e6d:f46e:4dea prefixlen 64 scopeid 0x20 ether dc:a6:32:04:2a:9c txqueuelen 1000 (Ethernet) RX packets 428 bytes 38739 (37.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 1520 (1.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) 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

veth05f2b7e: flags=4163 mtu 1500 inet6 fe80::f480:67ff:fe18:6e96 prefixlen 64 scopeid 0x20 ether f6:80:67:18:6e:96 txqueuelen 0 (Ethernet) RX packets 10 bytes 700 (700.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 48 bytes 5670 (5.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth0d17bc0: flags=4163 mtu 1500 inet6 fe80::7c1e:a1e4:8760:b726 prefixlen 64 scopeid 0x20 inet6 fe80::e4a5:76ff:fe1f:2a40 prefixlen 64 scopeid 0x20 ether e6:a5:76:1f:2a:40 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 86 bytes 12948 (12.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethf4fa3c3: flags=4163 mtu 1500 inet6 fe80::6273:fa3f:d659:8bc1 prefixlen 64 scopeid 0x20 inet6 fe80::bc54:91ff:fe32:d634 prefixlen 64 scopeid 0x20 ether be:54:91:32:d6:34 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 73 bytes 11189 (10.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

有人可以帮我解决这个问题吗？

Answer 1

似乎默认 Docker 使用本地网络，我认为将所有网络设备仅移动到 IP6，

如果您不定义网络并将所有服务设置为使用它，这似乎是默认行为。

更改 docker-compose 文件以包含：网络：您的网络名称：

并嵌套在每个服务下：网络： - 你的网络名称

...给了我 ip4 连接。

docker 在 raspberry pi 4 raspbian buster 上安装后无法访问网络

Network unreachable after docker install on raspberry pi 4 raspian buster

docker

networking

docker-compose

raspbian

raspberry-pi4