How to workaround network issues on systems running Docker

How to workaround network issues on systems running Docker

Context:


Docker is a container software, which creates a virtual environment in which to easily develop, deploy, and run applications. To do this, the Docker instances run on a virtual network interface, which is configured to the IP range 172.17.0.0/16 by default.


The issue:


This default Docker IP range overlaps with the IP range used for the university's IllinoisNet wireless network. The Docker system only listens for packets in this IP range on its virtual network interface, and NOT on the system's regular physical network interface. So any packets sent to the Docker system from the relevant IllinoisNet range will never be received by the Docker system. And any packets sent to the relevant IllinoisNet range from the Docker system will never leave the Docker system.


The fix:


Configure Docker to use a different subnet for its virtual network interface. The safest bet would be to use the private IP range 192.168.0.0/16, or better yet, a smaller sub-range, such as 192.168.5.0/24.

For reference, here is a list of IP ranges utilized by the university. To minimize issues, you would want to avoid overlapping your Docker subnet with these ranges:

Here are a couple of links with information regarding how to accomplish this. This is advanced configuration. The Engineering IT Helpdesk does not support Docker or Docker configuration. Please do your research before attempting this.



Short URL for this page: http://go.illinois.edu/docker-fix



Keywords:network wireless docker container software   Doc ID:84430
Owner:Matthew S.Group:University of Illinois Engineering IT
Created:2018-07-31 20:53 CDTUpdated:2018-07-31 20:54 CDT
Sites:University of Illinois Engineering IT
Feedback:  0   0