Official Repository

Last pushed: 2 hours ago
Short Description
The WordPress rich content management system can utilize plugins, widgets, and themes.
Full Description

Supported tags and respective Dockerfile links

Quick reference

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.

Image Variants

The wordpress images come in many flavors, each designed for a specific use case.

wordpress:<version>

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.

wordpress:alpine

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 git or 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).

Docker Pull Command

Comments (95)
lisyatanz
2 hours ago

website recommendations: https://goo.gl/i1CHDX

port22
a month ago

please consider making an alpine-fpm7-nginx variant (using sockets)!

egoncalves
2 months ago

If someone needs a video on how to setup this Official Wordpress with Mariadb docker's container using kitematic (alpha) in linux with data persistence and container linking, check this one: https://youtu.be/DqqVRIXZwzc

csandanov
3 months ago

For a complete WordPress stack see https://github.com/wodby/docker4wordpress

speerit23
4 months ago

it seems like tag php7.1-fpm is not upgraded to latest 4.7.5 any ideas?

bgordon
4 months ago

@homersim1:
yw

I don't really understand your question. I fire up a separate mariadb container for each app instance that requires one (Wordpress, Nextcloud, etc.). The performance hit is negligible. nginx-proxy and letsencrypt only require one instance each to handle everything.

IMO, it is best to do it this way even though you may end up with many mariadb containers. Plus, backups are easy -- just copy the compose directory somewhere, then you can restore to a fresh docker install anywhere with everything right where you left off.

homersim1
4 months ago

@bgordon:
thanks for your fast reply.

Iam wondering what is the difference? I am running already a mariadb container, letsencrypt container (both from linuxserver) connected to wordpress container.
So i really like your approach but it would mean to have some functions doubled. Can I find somewhere what is added/changed to make it working?

Thanks

bgordon
4 months ago

To clarify on my previous post in case it wasn't obvious, that's using jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion.

bgordon
4 months ago

@homersim1:

version: '2'

services:

  db-wordpress:
    image: mariadb
    container_name: db-wordpress
    volumes:
      - ./db-wordpress:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=wordpress
      - MYSQL_DATABASE=wordpress
      - MYSQL_USER=wordpress
      - MYSQL_PASSWORD=wordpress
    networks:
      - proxy-tier
    restart: always

  wordpress:
    depends_on:
      - db-wordpress
    image: wordpress
    container_name: wordpress
    environment:
      - WORDPRESS_DB_HOST=db-wordpress:3306
      - WORDPRESS_DB_PASSWORD=wordpress
      - VIRTUAL_HOST=www.example.com
      - LETSENCRYPT_HOST=www.example.com
      - LETSENCRYPT_EMAIL=admin@example.com
    networks:
      - proxy-tier
    restart: always

networks:
  proxy-tier:
    external:
      name: nginx_proxy_network_whatever_its_called
homersim1
4 months ago

Do you have a configuration example for running your worpress docker behind a nginx reverse proxy?

Thanks