搭建PHP Docker开发环境：解决www-data运行时的403访问拒绝错误

Hey there! Let's tackle that frustrating HTTP 403 error you're getting when running your PHP app as www-data in your Docker environment. I've dealt with similar issues while setting up Dockerized PHP stacks, so here's a step-by-step breakdown of the most common fixes:

The #1 cause of 403s in this scenario is incorrect permissions that block www-data from accessing or reading your app files. Here's how to fix it:

• First, ensure the mounted source directory is owned by www-data (you can add this to your Dockerfile or run it inside the container):

  chown -R www-data:www-data $SRC_PATH
  

• Set safe default permissions for files and directories:

  # Give directories read/write/execute for owner, read/execute for others
  find $SRC_PATH -type d -exec chmod 755 {} \;
  # Give files read/write for owner, read for others
  find $SRC_PATH -type f -exec chmod 644 {} \;
  

• For directories that need write access (like storage, uploads, or cache folders), loosen permissions slightly:

  chmod -R 775 $SRC_PATH/storage
  

Double-check that your .env and docker-compose.yml are correctly mapping your project path:

• Ensure your .env has a valid absolute path for SRC_PATH, e.g.:

  SRC_PATH=/home/your-user/projects/your-php-app
  

• Confirm your docker-compose.yml is using the environment variable correctly for mounting:

  services:
    php:
      build: .
      volumes:
        - ${SRC_PATH}:/var/www/html # Match the path your web server expects
      environment:
        - SRC_PATH=${SRC_PATH}
  

• On Windows/WSL or macOS, make sure the host directory is accessible to Docker (enable file sharing in Docker Desktop if needed).

If your web server (Nginx or Apache) isn't pointing to the right directory or has restrictive rules, it'll throw a 403:

For Nginx: #

Make sure your server block points to the correct root directory (e.g., public for frameworks like Laravel) and allows PHP execution:

server {
    listen 80;
    root /var/www/html/public; # Adjust this to your app's web root
    index index.php index.html;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ \.php$ {
        fastcgi_pass php:9000; # Match your PHP-FPM service name
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

For Apache: #

Enable mod_rewrite and set proper directory permissions:

<Directory /var/www/html/public>
    AllowOverride All
    Require all granted
</Directory>

Also confirm your Apache process is running as www-data (this is default for most images, but it never hurts to check).

Ensure PHP-FPM is configured to run as www-data so it can access the same files as your web server:

• Open your PHP-FPM config file (usually www.conf in /etc/php/<version>/fpm/pool.d/) and verify these lines:

  user = www-data
  group = www-data
  listen.owner = www-data
  listen.group = www-data
  

• Restart PHP-FPM after making changes:

  service php-fpm restart
  

If you're running Docker on a Linux machine, SELinux or AppArmor might be blocking access to your mounted directory:

• Test temporarily by disabling SELinux (don't leave this off permanently):

  setenforce 0
  

• If that fixes the 403, add a permanent SELinux rule to allow access:

  chcon -Rt httpd_sys_content_t $SRC_PATH
  

• Alternatively, you can disable AppArmor/SELinux for the service in docker-compose.yml:

  services:
    php:
      security_opt:
        - label:disable
  

Start with the permission and mounting checks first—those are the most frequent culprits. Let me know if you hit any snags!

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