wp-content is owned by root on creation

[drewcovi]

It seems we should be able to mount themes and plugins and uploads separately, but for some reason it appears that when I remove and re-create wordpress using docker-compose, wp-content is always owned by root.

 wordpress:
 depends_on:
 - db
 image: wordpress:latest
 container_name: wordpress
 restart: always
 volumes:
 - ./wordpress/themes:/var/www/html/wp-content/themes:rw
 - ./wordpress/plugins:/var/www/html/wp-content/plugins:rw
 - ./wordpress/uploads.ini:/usr/local/etc/php/conf.d/uploads.ini
 environment:
 WORDPRESS_DB_HOST: db
 WORDPRESS_DB_USER: xxx
 WORDPRESS_DB_PASSWORD: xxx 
 WORDPRESS_DB_NAME: xxx
 VIRTUAL_HOST: xxx

-rw-r--r-- 1 www-data www-data 4.7K Nov 30 2017 wp-trackback.php
-rw-r--r-- 1 www-data www-data 8.3K Nov 30 2017 wp-mail.php
-rw-r--r-- 1 www-data www-data 3.3K Nov 30 2017 wp-load.php
-rw-r--r-- 1 www-data www-data 369 Nov 30 2017 wp-blog-header.php
-rw-r--r-- 1 www-data www-data 420 Nov 30 2017 index.php
-rw-r--r-- 1 www-data www-data 3.0K Aug 17 2018 xmlrpc.php
-rw-r--r-- 1 www-data www-data 20K Jan 1 2019 license.txt
-rw-r--r-- 1 www-data www-data 3.8K Jan 9 2019 wp-cron.php
-rw-r--r-- 1 www-data www-data 6.8K Jan 12 2019 wp-activate.php
-rw-r--r-- 1 www-data www-data 2.5K Jan 16 2019 wp-links-opml.php
-rw-r--r-- 1 www-data www-data 31K Jan 16 2019 wp-signup.php
-rw-r--r-- 1 www-data www-data 2.3K Jan 21 2019 wp-comments-post.php
-rw-r--r-- 1 www-data www-data 19K Mar 28 19:04 wp-settings.php
-rw-r--r-- 1 www-data www-data 7.3K Apr 8 22:59 readme.html
-rw-r--r-- 1 www-data www-data 39K Jun 10 13:34 wp-login.php
drwxr-xr-x 9 www-data www-data 4.0K Sep 5 01:08 wp-admin
drwxr-xr-x 20 www-data www-data 12K Sep 5 01:08 wp-includes
drwxr-xr-x 1 root root 4.0K Sep 12 09:32 ..
drwxr-xr-x 4 root root 4.0K Sep 24 02:17 wp-content
-rw-r--r-- 1 www-data www-data 234 Sep 24 02:17 .htaccess
-rw-r--r-- 1 www-data www-data 2.8K Sep 24 02:17 wp-config-sample.php
-rw-r--r-- 1 www-data www-data 3.2K Sep 24 02:17 wp-config.php
drwxrwxrwx 5 www-data www-data 4.0K Sep 24 02:17 .

[wglambert]

If you mount the parent directory as well it should have appropriate permissions

#426 (comment)

So when just the subdirectories of wp-content/ are mounted it makes wp-content owned by root and docker-entrypoint.sh doesn't do a wordpress install as it detects present files and assumed the wp-content is fully populated

[drewcovi]

So is that a workaround? It seems like a common need and something that could be checked for in entrypoint.sh

[wglambert]

The parent wp-content directory doesn't exist in the image before the entrypoint is executed. So when subdirectories are mounted under it, then it needs to be created and is done so as root

[drewcovi]

makes sense. i just assumed there could be a one line script to just check for that folder afterwards and chown accordingly... but I'm admittedly somewhat green here.

[lapkritinis]

I support it.. I do it a bit differently - I copy in advance wp-content folder and my chown commands gets totally ignored:

Here is my dockerfile:

FROM wordpress:5-php7.1-apache
COPY files/ /var/www/html
RUN chown -R www-data:www-data /var/www/html

I still get everything as root:root
Running under ECS fargate, there is no option to mount anything.

[filipecorrea]

I changed my docker-compose.yml to mount wp-content instead of the child directories but the problem persists.

[thomasplevy]

Does anyone have a working example of a docker-compose.yml that actually allows mounting a shared theme/plugin without causing permission issues in the docker container?

I've been running in circles for a long time now trying to switch to Docker for automated e2e testing and I just can't get past these permissions issues.

I now have it so it's mounting directories as 1000:1000 (the uid/gid of my host user) but the filesystem still doesn't work right as a result.

Edit: word

[01e9]

The place to start experimenting/debugging

wordpress/docker-entrypoint.sh

Lines 30 to 31 in 0df5de0

	user="${APACHE_RUN_USER:-www-data}"
	group="${APACHE_RUN_GROUP:-www-data}"

[diogoterremoto]

I'm my case, because I'm only binding volumes in docker-compose, I've solved the issue by chowning before running Apache, like this:

command: bash -c "/bin/chown -R www-data:www-data /var/www/html && apache2-foreground"

---

EDIT: For some reason, the above doesn't work, as it fails to copy the contents from /usr/src/wordpress on container first run.