wordpressEstimated reading time: 11 minutes
The WordPress rich content management system can utilize plugins, widgets, and themes.
GitHub repo: https://github.com/docker-library/wordpress
Supported tags and respective
Where to file issues:
the Docker Community
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.
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
-e WORDPRESS_DB_USER=...(defaults to “root”)
-e WORDPRESS_DB_PASSWORD=...(defaults to the value of the
MYSQL_ROOT_PASSWORDenvironment variable from the linked
-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_NONCE_SALT=...(default to unique random SHA1s)
-e WORDPRESS_DEBUG=1(defaults to disabled, non-empty value will enable
-e WORDPRESS_CONFIG_EXTRA=...(defaults to nothing, non-empty value will be embedded verbatim inside
wp-config.php-- especially useful for applying extra configuration values this image does not provide by default such as
WP_ALLOW_MULTISITE; see docker-library/wordpress#142 for more details)
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://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
$ docker run --name some-wordpress -e WORDPRESS_DB_HOST=10.1.2.3:3306 \ -e WORDPRESS_DB_USER=... -e WORDPRESS_DB_PASSWORD=... -d wordpress
When running WordPress with TLS behind a reverse proxy such as NGINX which is responsible for doing TLS termination, be sure to set
X-Forwarded-Proto appropriately (see “Using a Reverse Proxy” in “Administration Over SSL” in upstream’s documentation). No additional environment variables or configuration should be necessary (this image automatically adds the noted
HTTP_X_FORWARDED_PROTO code to
wp-config.php if any of the above-noted environment variables are specified).
If your database requires SSL, WordPress ticket #28625 has the relevant details regarding support for that with WordPress upstream. As a workaround, the “Secure DB Connection” plugin can be extracted into the WordPress directory and the appropriate values described in the configuration of that plugin added in
As an alternative to passing sensitive information via environment variables,
_FILE may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in
/run/secrets/<secret_name> files. For example:
$ docker run --name some-wordpress -e WORDPRESS_DB_PASSWORD_FILE=/run/secrets/mysql-root ... -d wordpress:tag
Currently, this is supported for
docker stack deploy or
version: '3.1' services: wordpress: image: wordpress restart: always ports: - 8080:80 environment: WORDPRESS_DB_HOST: db WORDPRESS_DB_USER: exampleuser WORDPRESS_DB_PASSWORD: examplepass WORDPRESS_DB_NAME: exampledb db: image: mysql:5.7 restart: always environment: MYSQL_DATABASE: exampledb MYSQL_USER: exampleuser MYSQL_PASSWORD: examplepass MYSQL_RANDOM_ROOT_PASSWORD: '1'
docker stack deploy -c stack.yml wordpress (or
docker-compose -f stack.yml up), wait for it to initialize completely, and visit
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
Include pre-installed themes / plugins
Mount the volume containing your themes or plugins to the proper directory; and then apply them through the wp-admin webui. Ensure read/write/execute permissions are in place for the user.
- Themes go in a subdirectory in
- Plugins go in a subdirectory in
Running as an arbitrary user
When running WP-CLI via the
cli variants of this image, it is important to note that they’re based on Alpine, and have a default
USER of Alpine’s
www-data, whose UID is
82 (compared to the Debian-based WordPress variants whose default effective UID is
33), so when running
wordpress:cli against an existing Debian-based WordPress install, something like
--user 33:33 is likely going to be necessary. See docker-library/wordpress#256 for more discussion around this.
wordpress images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn’t have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it’s uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
This image variant does not contain WordPress itself, but instead contains WP-CLI.
The simplest way to use it with an existing WordPress container would be something similar to the following:
$ docker run -it --rm \ --volumes-from some-wordpress \ --network container:some-wordpress \ wordpress:cli user list
Generally speaking, for WP-CLI to interact with a WordPress install, it needs access to the on-disk files of the WordPress install, and access to the database (and the easiest way to accomplish that such that
wp-config.php does not require changes is to simply join the networking context of the existing and presumably working WordPress container, but there are many other ways to accomplish that which will be left as an exercise for the reader).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.library, sample, wordpress