Docker uses the 172.x.x.x ip space and Yale is also using this range for private ip space.
If you used the Docker official repo it would have created a docker0 interface with a 172.x.x.x interface. i.e.
sudo Ifconfig docker0
docker0: flags=4099<up,broadcast,multicast> mtu 1500
inet 172.x.x.x netmask 255.255.0.0 broadcast 0.0.0.0
This overlaps with 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> - sudo su -
- systemctl stop docker
- sudo su -
- Ifdown ifdown docker0
- ifconfig docker0 down
- cat << EOF >> /etc/sysconfig/network-scripts/ifcfg-docker0
TYPE=Bridge
DEVICE=docker0
NETMASK=255.255.252.0
IPADDR=192.168.5.1
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
DELAY=0
EOF - Ifup ifup docker0
- systemctl start docker
| 