it’s really weir things to me. I have a container A run with “-p 8080:80”, and a container B ( on the same host ) directly visit host-ip:8080, then log says: NO ROUTE TO HOST. I test the following things: 1.from within container B, “telnet host-ip 8080” also print “NO ROUTE TO HOST”; 2.from my l…

Could you please paste how you started the containers. In case you used docker stack deploy or docker-compose up, please paste the compose file as well. In case you are using DockerForMac (or some similar setup, which uses a virtual machine), make sure that the IP you are refering to is the one of …

Thanks. Since the dev network can’t be reached from the Internet, so sorry for can’t paste the exact script. I can describe the steps more specific: 1. server runs docker has ip like '192.168.10.4', name it 'appHost' 2. Since it is just for some test, I use some "docker run --name nginx_tmp -d -p …

I have same problem. I have three hosts. 192.168.50.40 - docker swarm manager 192.168.50.41 - docker swarm worker, PostgreSQL installed. 192.168.50.42 - docker swarm worker In host 192.168.50.41, I’ve installed PostgreSQL(native, not docker). Webapp containers that are running on other two hos…

Today I tried on CentOS7: I added a rich rule in /etc/firewalld/zones/public.xml to include my container’s IP <rule family="ipv4"> <source address="172.18.0.0/16"/> <accept/> </rule> then I restartted firewalld: systemctl restart firewalld After that, my container could connect t…

Thanks! This worked like a charm! One thing that is worth to comment is that this rule is regarding to the default docker network (172.18.0.0/16). If you have a container running on a different network, lets say 173.16.0.0/16 then it is necessary to add one rule for it as well.

I’d changed my OS from CentOS to Ubuntu16.04 and I met this problem again… :’( In my container, I can ssh to any other host nodes in the swarm, but I can not ssh to the host that is running this container. # ssh 192.168.53.31 ssh_exchange_identification: read: Connection reset by peer UFW(Ubunt…

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.

Hello, Do you ask the difference between 172.17.0.0/16 and 172.17.0.0(without /16)? As far as I know, 172.17.0.0/16 means the network prefix is first 16 bits. This matches all IP addresses that begin with 172.17, for example, 172.16.20.30, while 172.17.0.0 matches only that address.

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

General

antoinetran (Antoinetran) October 5, 2017, 2:56pm 4

This is a “known” bug. Everyone can access in this port, except for container in the same host. You have to allow it with firewall (yes this is a firewall/docker issue).

Topic		Replies	Views
(solved)A container cant access another container via name or IP although in same network General docker	3	9429	August 11, 2020
No route to host, but ping works...? General	0	5463	July 16, 2018
Cannot access container via external IP but can access via host IP with port General	1	5256	October 6, 2020
Not able to connect from docker container to local host General docker	5	8304	March 2, 2018
Container Not Routing to / from Host IP General	0	1880	April 11, 2018

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

Related topics