white-yacht-56857
10/25/2022, 2:36 PMfast-garage-66093
10/25/2022, 3:43 PMwhite-yacht-56857
10/25/2022, 4:29 PMwide-mechanic-33041
10/25/2022, 4:34 PMfast-garage-66093
10/25/2022, 4:37 PMnetworks.yaml
is about the bridged and shared interfaces only; @white-yacht-56857's issue seems to be with the internal docker network inside the VM. Since it overlaps with his local network, he is not able to route packets to other machines on the local net.$ rdctl shell ip a show docker0
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
link/ether 02:42:27:6b:85:8f brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
wide-mechanic-33041
10/25/2022, 4:41 PMfast-garage-66093
10/25/2022, 5:04 PM$ echo '{"bip":"172.20.0.1/16"}' | rdctl shell sudo tee /etc/docker/daemon.json
$ rdctl shell ip a show docker0
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
link/ether 02:42:5f:b0:5f:23 brd ff:ff:ff:ff:ff:ff
inet 172.20.0.1/16 brd 172.20.255.255 scope global docker0
valid_lft forever preferred_lft forever
bip
must be a valid gateway address, so you can't specify x.y.z.0/nn
. Don't ask me how I know! 😄daemon.json
, but we might in the future, so blindly overwriting it as I do above may create problems.