can't copy into var/www/html

[Amblomeke]

my minimalist example:

FROM wordpress:latest

COPY . /var/www/html

This fails to run. The build succeeds but when I actually go into bash and look, the files are not there. If I instead COPY to /usr/src/wordpress, then it succeeds, but the contents of /var/www/html remain the same, so I'm not anywhere closer to my goal, since I assume that I need my files to be in the latter folder.

Thanks for any help.

[tianon]

This would be because /var/www/html is a VOLUME, since that's where we store the "mutable state" for WordPress. (/usr/src/wordpress gets copied over to /var/www/html on first run, and then the user is expected to manage WordPress updates in the standard "WordPress way" through either the web UI or via taking the newer tarball and extracting it manually)

See also

wordpress/apache/Dockerfile

Line 21 in 61dd78c

VOLUME /var/www/html

and

wordpress/apache/docker-entrypoint.sh

Lines 22 to 46 in 61dd78c

	if ! [ -e index.php -a -e wp-includes/version.php ]; then
	echo >&2 "WordPress not found in $(pwd) - copying now..."
	if [ "$(ls -A)" ]; then
	echo >&2 "WARNING: $(pwd) is not empty - press Ctrl+C now if this is an error!"
	( set -x; ls -A; sleep 10 )
	fi
	tar cf - --one-file-system -C /usr/src/wordpress . | tar xf -
	echo >&2 "Complete! WordPress has been successfully copied to $(pwd)"
	if [ ! -e .htaccess ]; then
	# NOTE: The "Indexes" option is disabled in the php:apache base image
	cat > .htaccess <<-'EOF'
	# BEGIN WordPress
	<IfModule mod_rewrite.c>
	RewriteEngine On
	RewriteBase /
	RewriteRule ^index\.php$ - [L]
	RewriteCond %{REQUEST_FILENAME} !-f
	RewriteCond %{REQUEST_FILENAME} !-d
	RewriteRule . /index.php [L]
	</IfModule>
	# END WordPress
	EOF
	chown www-data:www-data .htaccess
	fi
	fi

.

[Amblomeke]

I have a custom theme I need to upload to that directory though and I can't do so if the directory is read-only.

[tianon]

Your custom theme needs to be uploaded into /usr/src/wordpress/wp-content/themes, which will be copied along with the rest of the WordPress source code at runtime over to /var/lib/www.

ie:

FROM wordpress

COPY . /usr/src/wordpress/wp-content/themes/my-theme

[edevil]

What about wordpress plugins? Is there a way to have them installed automatically?

EDIT: nvm, I think we just need to copy them to /usr/src/wordpress/wp-content/plugins

[tianon]

Yeah, you're exactly right -- if you copy your plugins to /usr/src/wordpress/wp-content/plugins, they should be installed automatically after the container is initialized.

[yamila-moreno]

Hi! I think this is the proper place to ask about this. It's about a custom theme.
In my Dockerfile I copy wp-content into /usr/src/wordpress/wp-content (I've double checked that the theme is located inside the running containter), but it's not copied in /var/www/html.

The first time I run the container it worked, but now it complains it doesn't find the theme (which is right, as is not there).

I'd appreciate any hint, thanks in advance for your work and for sharing :)

[tianon]

@yamila-moreno if your goal is to bake a custom image which will install your theme alongside the WordPress install, then putting it in /usr/src/wordpress/wp-content is correct -- if you're looking for a local "theme development" solution, you should be able to simply bind-mount your theme directory into /var/www/html/wp-content appropriately and WordPress will be installed around it (and then you can restart/recreate the container at will and continue developing)

[yamila-moreno]

Hi @tianon thanks for your answer. I continued the troubleshooting and it was my mistake in the docker-file.yml. I was trying to ensure that the new content uploaded to the blog would persist if the container were stoped or removed, so I tried to map wp-content to my host (thinking in the uploads dir). It doesn't work! ^_^
Again thanks for your time :D

[nalroff]

This is a hindrance to doing theme development since you'd have to restart your container every time you made a change. It would be nice to be able to declare the custom theme (or plugin, for that matter) as a volume so you can make changes on the host file system.

Doing so works after the initial run/copy, but it breaks if WP is not already installed in the container.

Disclaimer: I just started playing with Docker this week, so I could have it completely wrong.

[tianon]

@nalroff as I noted in my comment above (#146 (comment)), for theme development, I usually just bind-mount my local theme directory directly into /var/www/html/wp-content so that it's automatically picked up by WordPress and I can update it live, refreshing to see the new content, something like:

$ docker run ... -v "$PWD":/var/www/html/wp-content/themes/my-cool-theme:ro ... wordpress

or via docker-compose.yml:

  volumes:
    - .:/var/www/html/wp-content/themes/my-cool-theme:ro

[nalroff]

@tianon Interesting... this doesn't seem to work for me. The container cannot copy the wordpress files from /usr/src/wordpress into /var/www/html because /var/www/html/wp-content/themes/my-cool-theme already exists as a volume with my host machine's user as the owner using docker-compose.yml. I'd rather not adjust the permissions on my files to 777 or change groups or anything like that. What am I missing?

Again, I'm not hurting too bad about this... it works fine if I comment out my volumes, let the container start up once, and then uncomment them and re-up them. I have to repeat the process if I docker-compose down, of course.

Here is my docker-compose.yaml:

version: '2'
services:
  mysql:
    image: mysql:5.7
    environment:
    - MYSQL_ROOT_PASSWORD=password
    - MYSQL_DATABASE=somedb
  web:
    image: wordpress
    environment:
      WORDPRESS_DB_HOST: mysql
      WORDPRESS_DB_NAME: somedb
      WORDPRESS_DB_USER: root
      WORDPRESS_DB_PASSWORD: password
    links:
    - mysql
    ports:
    - 127.0.0.3:8080:80
    volumes:
    - ./wp-content/themes/tpb-2017:/var/www/html/wp-content/themes/tpb-2017

[tianon]

Since the original question here is solved, I'm going to close.

In the future, these sorts of questions/requests would be more appropriately posted to the Docker Community Forums, the Docker Community Slack, or Stack Overflow.

@nalroff on your specific issue, I can't reproduce -- I've been using this method for theme development with this image for quite some time now (and was the main reason we switched from using rsync to using tar for copying the source into the volume back in #61 (comment))