Page Comparison

Docker uses the 172.x17.x.x ip space and Yale is also using this range for private ip spaceIP space, which conflicts with important Yale campus resources, including the Yale VPN.

If you used using the Docker official repo, it would will have created a docker0 interface with a 172.x17.x.x interface, e. i.e.
sudo Ifconfig docker0
docker0: flags=4099<up,broadcast,multicast> mtu 1500
inet 172.x.x.x netmask g.

$ netstat -nr | grep '172.17'
172.17.0.0 0.0.0.0 255.255.0.0

 U 0

 0

 0

 docker0

This overlaps with campus Yale networks, and causes routing to fail since it tries to route out of the docker0 interface and go’s nowhere. The fix is to just use a 192.x.x.x ip on the docker0 inteface
Do the following.
</up,broadcast,multicast>

change the default network used by the Docker interface.

$ sudo su -
$ cat << EOF >> /etc/docker/daemon.json
{
"bip": "10.221.31.1/24",
"fixed-cidr": "10.221.31.1/25"
}
EOF
$ systemctl restart docker

You may need to reboot your Spinup virtual machine to clear any lingering entries in the system's network routing table in order for the fix to take effect.