docker-compose up后主机端口映射失效，Node应用无法访问求助

Let's walk through this issue systematically—here are the key checks I'd run to figure out why your app isn't accessible despite the port mapping showing as correct:

• Verify the container is actually running
  First, run docker ps to check if your target container is in the Up state. If it's exited or restarting, grab the logs with docker logs <container-name-or-id> to spot startup errors—common culprits include missing dependencies, syntax errors in your Node code, or misconfigured environment variables.

• Confirm the app is listening on 0.0.0.0:8000 inside the container
  Sometimes the port mapping looks right, but the app isn't actually listening internally. Exec into the container with docker exec -it <container-name-or-id> sh (use bash if your image includes it), then run netstat -tulpn | grep 8000 or ss -tulpn | grep 8000. You should see output showing Node bound to 0.0.0.0:8000—if it's only listening on 127.0.0.1, that's the problem (even though you thought it was set to 0.0.0.0, double-check your Node code's listen call!).

• Check for port conflicts on the host machine
  Docker might report the port mapping correctly, but another process on your host could be using port 8000. On Linux/macOS, run netstat -tulpn | grep 8000; on Windows, use netstat -ano | findstr :8000. If you see a non-Docker process here, kill it or adjust your docker-compose port mapping to something like 8001:8000 and try accessing http://localhost:8001.

• Rule out firewall or network issues

  • On Linux, check if ufw or iptables is blocking port 8000. Temporarily disable the firewall (e.g., sudo ufw disable) to test—if access works, add a rule to allow traffic on 8000.
  • On Windows/macOS with Docker Desktop, firewall settings might be blocking the port. Also, try restarting Docker Desktop or resetting its network configuration (look for the "Reset" option in Docker settings) to fix potential network stack glitches.

• Check Docker version compatibility
  Your Docker version (17.12.0-ce) is quite old (released in 2017) and has known bugs around port mapping and network handling. If all other checks pass, upgrading to a newer stable version (like 20.x or 24.x) could resolve the issue—older versions sometimes have quirks that get fixed in updates.

• Double-check your docker-compose.yml configuration
  Ensure your ports entry is formatted correctly (e.g., ports: - "8000:8000"—quotes can matter in some environments) and that you haven't accidentally swapped the host and container ports (it's host-port:container-port). Also, confirm the service's command or entrypoint isn't overriding the Dockerfile's startup command and failing to launch the Node app.

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