nextcloud-docs/wordpress/README.md

Supported tags and respective Dockerfile links

• 4.7.5-apache, 4.7-apache, 4-apache, apache, 4.7.5, 4.7, 4, latest, 4.7.5-php5.6-apache, 4.7-php5.6-apache, 4-php5.6-apache, php5.6-apache, 4.7.5-php5.6, 4.7-php5.6, 4-php5.6, php5.6 (php5.6/apache/Dockerfile)
• 4.7.5-fpm, 4.7-fpm, 4-fpm, fpm, 4.7.5-php5.6-fpm, 4.7-php5.6-fpm, 4-php5.6-fpm, php5.6-fpm (php5.6/fpm/Dockerfile)
• 4.7.5-fpm-alpine, 4.7-fpm-alpine, 4-fpm-alpine, fpm-alpine, 4.7.5-php5.6-fpm-alpine, 4.7-php5.6-fpm-alpine, 4-php5.6-fpm-alpine, php5.6-fpm-alpine (php5.6/fpm-alpine/Dockerfile)
• 4.7.5-php7.0-apache, 4.7-php7.0-apache, 4-php7.0-apache, php7.0-apache, 4.7.5-php7.0, 4.7-php7.0, 4-php7.0, php7.0 (php7.0/apache/Dockerfile)
• 4.7.5-php7.0-fpm, 4.7-php7.0-fpm, 4-php7.0-fpm, php7.0-fpm (php7.0/fpm/Dockerfile)
• 4.7.5-php7.0-fpm-alpine, 4.7-php7.0-fpm-alpine, 4-php7.0-fpm-alpine, php7.0-fpm-alpine (php7.0/fpm-alpine/Dockerfile)
• 4.7.5-php7.1-apache, 4.7-php7.1-apache, 4-php7.1-apache, php7.1-apache, 4.7.5-php7.1, 4.7-php7.1, 4-php7.1, php7.1 (php7.1/apache/Dockerfile)
• 4.7.5-php7.1-fpm, 4.7-php7.1-fpm, 4-php7.1-fpm, php7.1-fpm (php7.1/fpm/Dockerfile)
• 4.7.5-php7.1-fpm-alpine, 4.7-php7.1-fpm-alpine, 4-php7.1-fpm-alpine, php7.1-fpm-alpine (php7.1/fpm-alpine/Dockerfile)
• cli-1.1.0, cli-1.1, cli-1, cli, cli-1.1.0-php5.6, cli-1.1-php5.6, cli-1-php5.6, cli-php5.6 (php5.6/cli/Dockerfile)
• cli-1.1.0-php7.0, cli-1.1-php7.0, cli-1-php7.0, cli-php7.0 (php7.0/cli/Dockerfile)
• cli-1.1.0-php7.1, cli-1.1-php7.1, cli-1-php7.1, cli-php7.1 (php7.1/cli/Dockerfile)

Quick reference

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

• Where to file issues:
  https://github.com/docker-library/wordpress/issues

• Maintained by:
  the Docker Community

• Published image artifact details:
  repo-info repo's repos/wordpress/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/wordpress
  official-images repo's library/wordpress file (history)

• Source of this description:
  docs repo's wordpress/ directory (history)

• Supported Docker versions:
  the latest release (down to 1.6 on a best-effort basis)

What is WordPress?

WordPress is a free and open source blogging tool and a content management system (CMS) based on PHP and MySQL, which runs on a web hosting service. Features include a plugin architecture and a template system. WordPress is used by more than 22.0% of the top 10 million websites as of August 2013. WordPress is the most popular blogging system in use on the Web, at more than 60 million websites. The most popular languages used are English, Spanish and Bahasa Indonesia.

wikipedia.org/wiki/WordPress

How to use this image

$ docker run --name some-wordpress --link some-mysql:mysql -d wordpress

The following environment variables are also honored for configuring your WordPress instance:

• -e WORDPRESS_DB_HOST=... (defaults to the IP and port of the linked mysql container)
• -e WORDPRESS_DB_USER=... (defaults to "root")
• -e WORDPRESS_DB_PASSWORD=... (defaults to the value of the MYSQL_ROOT_PASSWORD environment variable from the linked mysql container)
• -e WORDPRESS_DB_NAME=... (defaults to "wordpress")
• -e WORDPRESS_TABLE_PREFIX=... (defaults to "", only set this when you need to override the default table prefix in wp-config.php)
• -e WORDPRESS_AUTH_KEY=..., -e WORDPRESS_SECURE_AUTH_KEY=..., -e WORDPRESS_LOGGED_IN_KEY=..., -e WORDPRESS_NONCE_KEY=..., -e WORDPRESS_AUTH_SALT=..., -e WORDPRESS_SECURE_AUTH_SALT=..., -e WORDPRESS_LOGGED_IN_SALT=..., -e WORDPRESS_NONCE_SALT=... (default to unique random SHA1s)

If the WORDPRESS_DB_NAME specified does not already exist on the given MySQL server, it will be created automatically upon startup of the wordpress container, provided that the WORDPRESS_DB_USER specified has the necessary permissions to create it.

If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:

$ docker run --name some-wordpress --link some-mysql:mysql -p 8080:80 -d wordpress

Then, access it via http://localhost:8080 or http://host-ip:8080 in a browser.

If you'd like to use an external database instead of a linked mysql container, specify the hostname and port with WORDPRESS_DB_HOST along with the password in WORDPRESS_DB_PASSWORD and the username in WORDPRESS_DB_USER (if it is something other than root):

$ docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 \
    -e WORDPRESS_DB_USER=... -e WORDPRESS_DB_PASSWORD=... -d wordpress

... via docker stack deploy or docker-compose

Example stack.yml for wordpress:

version: '3.1'

services:

  wordpress:
    image: wordpress
    ports:
      - 8080:80
    environment:
      WORDPRESS_DB_PASSWORD: example

  mysql:
    image: mysql:5.7
    environment:
      MYSQL_ROOT_PASSWORD: example

Run docker stack deploy -c stack.yml wordpress (or docker-compose -f stack.yml up), wait for it to initialize completely, and visit http://swarm-ip:8080, http://localhost:8080 or http://host-ip:8080 (as appropriate).

Adding additional libraries / extensions

This image does not provide any additional PHP extensions or other libraries, even if they are required by popular plugins. There are an infinite number of possible plugins, and they potentially require any extension PHP supports. Including every PHP extension that exists would dramatically increase the image size.

If you need additional PHP extensions, you'll need to create your own image FROM this one. The documentation of the php image explains how to compile additional extensions. Additionally, the wordpress Dockerfile has an example of doing this.

The following Docker Hub features can help with the task of keeping your dependent images up-to-date:

• Automated Builds let Docker Hub automatically build your Dockerfile each time you push changes to it.
• Repository Links can ensure that your image is also rebuilt any time wordpress is updated.