When running tools like like docker, podman, kubernetes, etc. Internal internal networks are setup set up that could collide with routed networks within the University of Waterloo’s infrastructure. If this collision happens, then any traffic that is supposed to route to those will stay on the given system. An example for this, if you are on VPN with the ip address 172.25.10.1, and you start a container or compose project, if docker allocates 172.25.0.0/20, your connection to the server will drop, as any traffic that was destined for you now gets directed to the docker network.
To prevent these issues from happening, campus Network Operations Centre (NOC) has reserved a subnet has been reserved so that it will not be routed. This can be used for containers. The network block that has been allocated is:
10.255.0.0/16
Which which contains 65,535 addresses that can be used for container networks. The various tools below use different default subnets and are configured differently. Known configurations are listed below, if . If there are any others that should be added, FAST members can edit this page, or a request can be made to document the specific tooling.
...