如何从Docker容器连接到主机端口？已试0.0.0.0:8080无效

Hey there! Let’s troubleshoot why your Docker container can’t connect to the 8080 port on your host machine. I’ve dealt with this exact scenario a bunch of times, so here’s a step-by-step guide to get it working:

Before diving into Docker settings, double-check that your server is truly listening on all interfaces (0.0.0.0:8080). Run this command on your host:

ss -tulpn | grep 8080

You should see output like LISTEN 0 128 0.0.0.0:8080 0.0.0.0:* or :::8080. If you only see 127.0.0.1:8080, your service is only listening locally and won’t be reachable from the container. Fix your server’s configuration to bind to 0.0.0.0 instead.

The address you use to connect from the container depends on your operating system:

• Linux:
  • The easiest way is to use host.docker.internal (Docker 20.10+ supports this by default). Try connecting to host.docker.internal:8080 from inside the container.
  • If that doesn’t work, find your host’s local LAN IP (e.g., via ip addr show eth0 or ip addr show wlan0). Look for an address like 192.168.x.x or 10.x.x.x, then connect to that IP:8080.
  • Alternatively, find the Docker bridge gateway IP with docker inspect <your-container-name> | grep Gateway, then use that IP (usually 172.17.0.1) to connect to port 8080.
• Windows/macOS:
  • Docker runs in a lightweight VM on these systems, so host.docker.internal is the official, supported way to reach the host. Just connect to host.docker.internal:8080 from your container.

More often than not, a firewall is blocking the connection from the Docker subnet to your host’s 8080 port.

• Linux (ufw):
  Allow traffic from Docker’s default subnet (172.17.0.0/16) to port 8080:

  sudo ufw allow from 172.17.0.0/16 to any port 8080
  

  If you’re using firewalld, run:

  sudo firewall-cmd --add-rich-rule='rule family="ipv4" source address="172.17.0.0/16" port port="8080" protocol="tcp" accept' --permanent
  sudo firewall-cmd --reload
  

• Windows/macOS:
  Open your system firewall settings and ensure your server application (or port 8080) is allowed to receive incoming connections from private networks (since Docker uses a private subnet).

• If you’re using a custom Docker network, make sure your container is attached to it. Custom networks usually have better DNS resolution, so host.docker.internal should work here too.
• Avoid using --network=host unless you really need it (it shares the host’s network stack with the container). If you do use it, you can connect directly to 127.0.0.1:8080 from inside the container, but this reduces isolation between the container and host.

Once you’ve tried the above steps, test the connection from inside the container to narrow down the issue:

1. Enter the container’s shell:

   docker exec -it <your-container-name> bash
   

2. Use curl or telnet to test the connection:

   curl host.docker.internal:8080
   # Or use your host's LAN IP
   curl 192.168.1.100:8080
   # Or test with telnet to check basic connectivity
   telnet host.docker.internal 8080
   

If telnet fails to connect, it’s a network/firewall issue. If curl gets an error response (like 404), the service is reachable but your server is returning an error—check your server’s logs in that case.

内容的提问来源于stack exchange，提问作者voltento