Docker新手求助：如何通过浏览器访问Apache+PHP容器？

Hey there! Let's break down how to get your Dockerized Apache/PHP stack accessible via browser—this is such a common gotcha when moving from traditional Apache to Docker, so you’re definitely not alone here.

Docker containers run in isolated network namespaces, which means their internal ports (like Apache’s default port 80) aren’t exposed to your host machine by default. You need to explicitly map a host port to the container’s Apache port using the -p flag when running your container.

For example, if you’re running a container from your custom Apache-PHP image:

docker run -d -p 8080:80 your-apache-php-image

Here, 8080 is the port on your host, and 80 is the port Apache listens on inside the container. Now you can access your app by visiting http://localhost:8080 (if you’re on the same machine) or your host’s local IP (like http://192.168.1.100:8080) in your browser.

If you’re using docker-compose, add the ports section to your service definition:

services:
  apache-php:
    image: your-apache-php-image
    ports:
      - "8080:80"

If you want to use a friendly hostname (e.g., http://myapp.local) instead of an IP:port combo, you can still use your host’s /etc/hosts file—with a small twist:

1. Edit your host’s /etc/hosts: Add a line that maps your desired hostname to your host’s loopback IP (or local network IP):

   127.0.0.1   myapp.local
   

2. Match the port mapping: If you mapped host port 8080, you’ll access it via http://myapp.local:8080. If you want to skip the port entirely (use port 80 directly), map host port 80 to container port 80:

   docker run -d -p 80:80 your-apache-php-image
   

   Now you can hit http://myapp.local just like you did with your non-Docker Apache setup.

Note: If you’re running multiple containers that need port 80, you’ll want to set up a reverse proxy (like Nginx in Docker) to route requests by hostname—but that’s a bit more advanced. For now, the port mapping + /etc/hosts trick should cover your needs.

Just to rule out any internal issues, double-check that Apache is actually listening on port 80 inside the container. Exec into the container and run:

docker exec -it your-container-name curl localhost

If you get HTML output, Apache is working as expected. If not, you’ll need to debug your Apache config inside the image.

• Connection refused? Make sure your port mapping is correct, and Apache is running inside the container (use docker logs your-container-name to check logs).
• 404 error? Ensure your web files are mounted into the container (using the -v flag or volumes in docker-compose) so Apache can find them.
• On Windows/macOS? Newer Docker Desktop versions handle localhost automatically, but if that doesn’t work, try using the Docker VM’s IP (you can find it in Docker Desktop settings).

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