-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container host unreachable inside Docker container #24370
Comments
Can you provide more information how you started your containers? (What options?), perhaps a minimal case to reproduce? |
I've the same issue. In my case, it was caused by my firewall rules. I solved it by adding:
Now I can do I think this should be solved by docker: whenever a bridge network is created, a firewall rule should be set to allow the container to reach the host on it's own exposed (host) port. Steps to reproduce (ubuntu 16.04 with docker 1.11.2 and 1.12.0, fedora 21 with docker 1.9.1): Solved it by:
Ideally (IMHO), docker should add this rule when a bridge or other network is created. |
Closing because we didn't get more information from OP |
Hi @thaJeztah , I don't think the issue should be closed. I've provided you with reproduce steps and a workaround. But I still think docker should solve this when setting up the iptables rules when a container or network is created. The problem is also with docker 1.12.1, on debian jessie, ubuntu 16.04 and fedora 21. |
Hey, I sadly can't remember anymore which application caused this issue and therefore can't reproduce it anymore. |
Hi @thaJeztah, can you please respond? Should I create a new issue or can this issue be re-opened? |
This is still an issue 4 years later. Any suggestions how to solve it that doesn't involve hard-coding interface names into my iptables rules? |
Output of
docker version
: Docker version 1.11.2, build b9f10c9Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
physical machine
* Problem description:*
I've got a docker container on host
183.83.83.83
(example)The A record of a subdomain mycontainer.example.com points to this IP.
A curl to
183.83.83.83
ormycontainer.example.com
gives HTTP status 200 and the correct website.However the same curl from inside every container on that host (to both the IP or hostname above) fails to connect:
This doesn't happen when trying this from a Docker container from another host or from the host itself.
What is going wrong here?
The text was updated successfully, but these errors were encountered: