you can remove the volume from either your image, get the upstream image to remove their volume definition, or you can rebuild your own copy of the upstream image without the volume definition and base your images off of that. you can fix the permissions on your host so they get copied in with those permissions directly. you can copy your files to a different directory and change the permissions there. These changes will not include the anonymous volume contents because they do not exist inside the temporary container filesystem, volumes are separateīecause of this behavior, you have the options to:. These changes can be seen with a docker diff if you do not delete the temporary containers (you can run a build with -rm=false to have them remain). When your run command completes, docker will capture the changes to the container. If you list the directory during this RUN command, you will see your changes applied, but those changes have been applied to the volume. Your command will run inside the container. The anonymous volume will be initialized from the contents of the image. That temporary container will have an anonymous volume mounted as you or a parent image specified inside the Dockerfile. Create a temporary container using the image definition as of the current point of the dockerfile. When a volume is defined in the Dockerfile, you can add files with a COPY or ADD command directly into the image. This issue is likely the result of a VOLUME definition inside the upstream Dockerfile. Running chmod same commands with bash inside the container: permissions are changed and my app is runningĪny idea, Am I missing something, maybe I should add root user somewhere in the Dockerfile ? Running chmod commands from dockerfile: permissions are changed but apache still complains about permission denied. 
and when I run chmod from container's bash, apache permission issues are gone and the app works well and run the container with docker run -p 8080:80 myname/symfony_apps:latest.Īpache log is flooded by permission denied errors, the strange thing that I've checked with ls -a and permissions are fine.
When I build this image with docker build -t myname/symfony_apps:latest. RUN chmod -R 777 /var/www/html/app/cache /var/www/html/app/logs RUN find /var/www/html/ -type d -exec chmod 755 \ & docker-php-ext-install intl mbstring \ĬOPY app/nf /etc/apache2/nf & apt-get install -y libicu-dev freetds-common freetds-bin unixodbc \ I'm building a Docker image for my Symfony app and I need to give permission to apache server to write into cache and log folders #Dockerfile
0 kommentar(er)
