Today, I took a flight and tried to use the in-flight Wi-Fi, but I was unable to login to the the network. Nothing loaded or opened. I poked around in ip route and found two different routes that conflicted created by the Docker daemon. Looking at the following route, there’s two routes: 172.19.0.0/23 and 172.19.0.0/16. These correspond to: 172.19.0.0 - 172.19.1.255 and 172.19.0.0 - 172.19.255.255.
1
2
3
4
5
6
7
8
9
10
11
12
| ip route
default via 172.19.0.1 dev wlp1s0 proto dhcp src 172.19.1.22 metric 600
172.18.0.0/16 dev br-71fb429d0dc2 proto kernel scope link src 172.18.0.1 linkdown
vvv
172.19.0.0/23 dev wlp1s0 proto kernel scope link src 172.19.1.22 metric 600
172.19.0.0/16 dev br-908cdaa5e0f4 proto kernel scope link src 172.19.0.1 linkdown
^^^
172.20.0.0/16 dev br-5432e3728889 proto kernel scope link src 172.20.0.1 linkdown
172.31.0.0/24 dev docker0 proto kernel scope link src 172.31.0.1 linkdown
|
And here’s the problematic networks:
1
2
3
4
5
6
7
8
9
| docker network ls
NETWORK ID NAME DRIVER SCOPE
908cdaa5e0f4 testwebsite_default bridge local
b112ed129840 bridge bridge local
cd3a9ccce4c5 host host local
2e34dc80f263 none null local
5432e3728889 quickstart bridge local
71fb429d0dc2 technowizardrynet_default bridge local
|
First step is to delete these networks docker network rm 908cdaa5e0f4 5432e3728889.
Then configure Docker to use a new range by adding the following to /etc/docker/daemon.json:
1
2
3
4
5
| {
"default-address-pools": [
{ "base":"172.31.0.0/16", "size":24 }
]
}
|
And restart docker: sudo systemctl restart docker. After that, you should be able to use Docker and the in-flight Wi-Fi.
Comments
Comments are currently unavailable while I move to this new blog platform. To give feedback, send an email to adam [at] this website url.