Finally, answering my own question. After some research I have found that it was IP masquerading that caused Docker to recognize client addresses incorrectly. The cause In my case, firewalld is configured to share internet connection with other machines in local network. This is accomplished by setting zone to public for the external interface (enp3s0) … Read more
Containers in different networks can not communicate with each other because iptables drop such packets. This is shown in the DOCKER-ISOLATION-STAGE-1 and DOCKER-ISOLATION-STAGE-2 chains in the filter table. sudo iptables -t filter -vL Rules can be added to DOCKER-USER chain to allow communication between different networks. In the above scenario, the following commands will allow … Read more
IPAM is the name of configuration section. IPAM is an acronym, that stands for IP Address Management. see more here: https://www.docker.com/blog/docker-networking-design-philosophy
The solution is simple! just remove the networks. like docker network rm <network Id> <space> <network Id> …. PS E:\repos\Github\officeconverter> docker network rm 92f7d20ed432 3f96cfb7b591 92f7d20ed432 3f96cfb7b591 PS E:\repos\Github\officeconverter> docker network ls NETWORK ID NAME DRIVER SCOPE 868c88a83bd6 bridge bridge local