如何通过主机公网IP从外部访问Linux主机上的Nginx Docker容器网页？

Let’s walk through the fixes and checks you need to get external access working, starting with the most obvious issue in your provided info:

1. You’re Missing Port Mapping (Critical First Fix) #

Looking at your docker container ls -a output, the running nginx2 container only shows 80/tcp in the PORTS column—this means the container’s port 80 isn’t mapped to any port on your Linux host. Docker doesn’t expose container ports to the outside world by default; you need to explicitly map them when starting the container.

To fix this, stop and remove your current container, then restart it with port mapping:

docker stop nginx2 && docker rm nginx2
docker run -d -p 80:80 --name nginx2 nginx

The -p 80:80 flag tells Docker to forward traffic from your Linux host’s port 80 to the container’s port 80. If port 80 is already in use on your host, you can use a different port like -p 8080:80 (then access it via your-public-ip:8080).

2. Check Linux Host Firewall Rules #

Even with port mapping, your Linux host’s firewall might be blocking incoming traffic to the mapped port. You’ll need to allow the port through:

• For ufw (common on Ubuntu/Debian):

  sudo ufw allow 80/tcp
  sudo ufw reload
  

• For firewalld (common on RHEL/CentOS):

  sudo firewall-cmd --add-port=80/tcp --permanent
  sudo firewall-cmd --reload
  

3. Verify Public IP Port Forwarding #

If your Linux host is on a local network (e.g., home server behind a router) or a cloud instance with a private internal IP, your public IP is likely tied to a gateway (router or cloud provider’s firewall). You need to set up port forwarding here too:

• Home Router: Log into your router’s admin interface, find the "Port Forwarding" or "Virtual Server" section, and forward public port 80 to your Linux host’s local IP address and port 80.
• Cloud Server: In your cloud provider’s console, update your security group rules to allow incoming TCP traffic on port 80 from any source (or restrict it to your Windows machine’s IP for better security).

4. Validate Container Internal Connectivity #

First, confirm the Nginx container is actually serving content. On your Linux host, run:

curl http://172.17.0.2

You should see the default Nginx welcome page. If not, restart the container (docker restart nginx2) or pull a fresh Nginx image (docker pull nginx) to rule out container-level issues.

5. Your Docker Bridge Network Looks Good #

From your docker network inspect bridge output, the default bridge network is configured correctly:

• com.docker.network.bridge.enable_ip_masquerade is set to true (enables traffic routing between the host and containers)
• host_binding_ipv4 is 0.0.0.0 (port mappings listen on all host network interfaces, including the public one)
  No issues here—your problem is almost certainly in the first three steps above.

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