Apache2 in docker container gives 403 on statically served files

I’m having a weird issue and am looking for ideas.

I’m running an apache2 debian image that serves some static files, and has a few redirect rules.
Running a container works fine, but results in 403 (permission denied) errors on any request (curl as well as browser).

  • Docker CLI env var value override not respected by container on startup
  • Writing Dockerfile for Dockerhub Automated builds
  • Accessing database that is running inside a docker container?
  • sudo service mongod start : mongod: unrecognized service
  • Disable access to LAN from docker container
  • Auto reconnect to RabbitMQ cluster after server restart
  • When I then exec into the container and perform an ls in a static file folder (such as css), those files are being served correctly on the next request.
    My current workaround is a startup script with a find /var/www/html/ -name '*'. This makes the container work as expected, with all the served files being accessible.

    • All the files have the correct owner (www-data) and permissions.
    • Docker version 1.7.1, but issue appeared also on 1.7.0
    • I’m running an Ubuntu VM, but my colleague reproduced this on a mac with docker machine.

    Whatever could be a reason for this behaviour?

  • filesystem layer verification failed for digest
  • Docker uses all memory and crashes the system
  • docker mysql on different port
  • GC overhead limit exceeded in Docker when trying to build project by sbt
  • Whenever gem 'failed to load command: rake'
  • Moving a Docker node to a different Azure account
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.