Docker HTTPD容器已正常运行，但网站无法访问，请求技术排查

Let’s work through this step by step to figure out why your simple Apache container isn’t accessible. Here are the key checks to run:

1. Verify the Container is Fully Running #

Your truncated container output shows it started, but let’s confirm it’s actually up and stable:

docker ps -a

Look for the container with ID 0912f4f7d1a8 — its STATUS should say something like Up X minutes (not Exited or Restarting). If it’s exited, skip straight to checking logs (step 5 below).

2. Check if Apache is Running Inside the Container #

Even if the container is up, the Apache process might have crashed. Jump into the container’s shell to verify:

docker exec -it 0912f4f7d1a8 bash

Once inside, check for active httpd processes:

ps aux | grep httpd

You should see multiple httpd entries (the main process + worker threads). If not, try starting Apache manually to surface errors:

apachectl start

3. Confirm Your HTML File Was Copied Correctly #

Path mix-ups are a common pitfall with COPY in Dockerfiles. Inside the container, check if your index.html exists and has the right content:

cat /usr/local/apache2/htdocs/index.html

If the file is missing or empty, double-check that your public-html directory is in the same folder as your Dockerfile when you ran docker build -t apachehttpd .. Your current COPY command looks correct, but it’s worth verifying there are no typos.

4. Validate Port Mapping & Local Access #

First, test access directly from the machine running Docker:

curl localhost:8080

If this returns nothing or an error:

• Check if port 8080 is already in use on your host:

  # Linux/macOS
  lsof -i :8080
  # Windows (PowerShell)
  netstat -ano | findstr :8080
  

  If another process is using 8080, restart the container with a different port:

  docker stop 0912f4f7d1a8
  docker run -dit -p 8081:80 apachehttpd
  

• If accessing from a remote machine (like a cloud server), ensure your host’s firewall/security group allows incoming traffic on port 8080.

5. Check Container Logs for Errors #

Apache logs will tell you exactly what’s going wrong. Pull the logs for your container:

docker logs 0912f4f7d1a8

Look for lines with error or failed — common issues include file permission errors (if the copied HTML file is owned by root and Apache can’t read it). If permissions are the problem, update your Dockerfile to set proper ownership:

FROM httpd:2.4
COPY ./public-html/ /usr/local/apache2/htdocs/
RUN chown -R daemon:daemon /usr/local/apache2/htdocs/

Then rebuild and restart the container:

docker build -t apachehttpd .
docker stop 0912f4f7d1a8
docker run -dit -p 8080:80 apachehttpd

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