Docker Network Requirements - v2023.04
Monofor is running in Docker service. Docker is has own network architecture and it is using below subnets by default.
Docker Bridge Networks | 172.17.0.0/16 |
Docker Swarm Networks | 10.0.0.0/8 |
Docker Network Topology
For production installation sometimes it cause an issue. Customers internal network and docker internal networks is overlapping. In the above topology showing example of container network addresses overlapping with the internal networks. But docker is giving an option to use specific subnets for docker services internal network.
Fixing this issue customer needs to define two(2) different subnets which is not used, not defined and not routed.
For Example:
Network | Used For | Description |
|---|---|---|
| Docker Service Network | It is used for docker internal bridge networks |
| Docker Swarm Overlay Network | It is used for Docker Swarm Service for overlay networks. |
In this example 192.168.5.0/24 and 192.168.6.0/24 are used for internally in the docker services. If these subnets are decided to use in the docker they won’t be able to use in the real network. Because if the same subnets are used in the real networks and some of the clients trying to reach MonoFor services they couldn’t be able to reach the services. Docker will not route back to clients traffic to real network.
These two networks should not be defined or configured within the customer network under any circumstances, whether at Layer 2 or Layer 3.