NO ROUTE TO HOST network request from container to host-ip:port published from other container

maannniii (Maannniii) October 15, 2018, 8:16am 11

Can you please explain why we should whitelist 172.18.0.0/16?
In my case I’ve whitelisted 172.17.0.0/16(docker0 interface) and 172.18.0.0/16(docker_gwbridge interface). Only after whitelisting both It’s working fine.

The same didn’t work when I whitelisted 172.17.0.0 and 172.18.0.0.

Topic		Replies	Views
No route to host, but ping works...? General	0	5380	July 16, 2018
(solved)A container cant access another container via name or IP although in same network General docker	3	8055	August 11, 2020
Cannot access container via external IP but can access via host IP with port General	1	4848	October 6, 2020
How to reach a container from another container without IP of dockerNAT? General	10	178312	October 13, 2016
Connect to docker host IP from container General docker	0	913	January 12, 2018

NO ROUTE TO HOST network request from container to host-ip:port published from other container

Related topics