Docker化Laravel应用时Apache服务器出现权限拒绝问题

Hey there! Let's tackle that Apache permission denied issue you're hitting while Dockerizing your Laravel app. Given your setup—Windows 10 + VirtualBox Ubuntu 16.x with shared folder at /media/sf_Projects—here are the most practical fixes to get you up and running:

1. Add your Ubuntu user to the vboxsf group #

VirtualBox shared folders default to the vboxsf group, and if your non-privileged user isn't part of this group, you'll run into basic read/write restrictions before Docker even gets involved. Run this command, then log out and back in to apply changes:

sudo usermod -aG vboxsf your-ubuntu-username

You can confirm your user is in the group with groups your-ubuntu-username.

2. Adjust shared folder mount permissions #

By default, shared folders might mount with strict root-owned permissions. Tweak the mount settings to match your user's UID/GID:

• Shut down your Ubuntu VM first
• Open VirtualBox Manager → Select your VM → Settings → Shared Folders
• Edit the sf_Projects share:
  • Check "Auto-mount" and "Make Permanent"
  • In "Mount Options", add uid=1000,gid=1000 (replace with your user's actual UID/GID—get these with id -u and id -g)
• Boot the VM, then verify permissions with ls -l /media/sf_Projects—it should now show your user as the owner.

3. Align Docker container Apache user permissions #

Apache in most PHP/Apache Docker images runs as the www-data user (UID 33, GID 33). To let it access your Laravel files, you have two solid options:

Option A: Match container www-data to your host user's UID/GID #

Add these lines to your Dockerfile to reassign the container's www-data user/group IDs to match your Ubuntu user:

# Replace 1000 with your actual UID/GID from `id -u`/`id -g`
RUN usermod -u 1000 www-data && groupmod -g 1000 www-data

This ensures the container's Apache user has the same permissions as your host user for the shared folder.

Option B: Fix Laravel directory permissions on the host #

Laravel needs write access to storage and bootstrap/cache directories. Run these commands in your Ubuntu VM:

cd /media/sf_Projects/your-laravel-app
# Set owner to your user and vboxsf group
sudo chown -R your-ubuntu-username:vboxsf .
# Give group write access to critical directories
sudo chmod -R 775 storage bootstrap/cache

For extra safety (instead of broad permissions), you can also run your Docker container with the vboxsf group ID mapped:

docker run -d \
  --group-add $(getent group vboxsf | cut -d: -f3) \
  -v /media/sf_Projects/your-laravel-app:/var/www/html \
  -p 8080:80 \
  your-apache-image

This adds the container's www-data user to the host's vboxsf group, granting it necessary write access.

4. Verify Docker mount paths #

Double-check your docker-compose.yml or run command uses the Ubuntu VM's path to the shared folder, not the Windows path. For example:

services:
  apache:
    image: php:7.4-apache
    volumes:
      # Correct: Ubuntu VM's shared folder path
      - /media/sf_Projects/your-laravel-app:/var/www/html
    ports:
      - 8080:80

Avoid using Windows paths like C:\Projects\...—Docker running in the Ubuntu VM can't resolve those.

5. Rule out SELinux (if enabled) #

Ubuntu 16.x doesn't enable SELinux by default, but if you've turned it on, it might block Docker's access to the shared folder. Test by temporarily disabling it:

sudo setenforce 0

If this fixes the issue, you'll need to add SELinux policies to allow Docker access to /media/sf_Projects, or keep SELinux disabled (not recommended for production).

After trying these steps, restart your Docker container and test your Laravel app—permission errors should be a thing of the past!

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