WordPress is one of the most versatile open source content management systems on the market. WordPress is built for high performance and is scalable to many servers, has easy integration via REST, JSON, SOAP and other formats, and features a whopping 15,000 plugins to extend and customize the application for just about any type of website.

https://www.wordpress.org/

$ curl -LO https://raw.githubusercontent.com/bitnami/bitnami-docker-wordpress/master/docker-compose.yml
$ docker-compose up

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami WordPress Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8 NOTE: RHEL images are not available in any public registry. You can build them on your side on top of RHEL as described on this doc.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 5-rhel-7, 5.1.1-rhel-7-r40 (5/rhel-7/Dockerfile)
• 5-ol-7, 5.1.1-ol-7-r41 (5/ol-7/Dockerfile)
• 5-debian-9, 5.1.1-debian-9-r44, 5, 5.1.1, 5.1.1-r44, latest (5/debian-9/Dockerfile)

Subscribe to project updates by watching the bitnami/wordpress GitHub repo.

To run this application you need Docker Engine >= 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.

WordPress requires access to a MySQL or MariaDB database to store information. We'll use our very own MariaDB image for the database requirements.

The recommended way to run WordPress is using Docker Compose using the following docker-compose.yml template:

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    volumes:
      - 'mariadb_data:/bitnami'
    environment:
      - MARIADB_USER=bn_wordpress
      - MARIADB_DATABASE=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
  wordpress:
    image: 'bitnami/wordpress:latest'
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - 'wordpress_data:/bitnami'
    depends_on:
      - mariadb
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes

volumes:
  mariadb_data:
    driver: local
  wordpress_data:
    driver: local

Launch the containers using:

$ docker-compose up -d

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

1. Create a network

$ docker network create wordpress-tier

2. Create a volume for MariaDB persistence and create a MariaDB container

$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_wordpress \
  -e MARIADB_DATABASE=bitnami_wordpress \
  --net wordpress-tier \
  --volume mariadb_data:/bitnami \
  bitnami/mariadb:latest

3. Create volumes for WordPress persistence and launch the container

$ docker volume create --name wordpress_data
$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e WORDPRESS_DATABASE_USER=bn_wordpress \
  -e WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --net wordpress-tier \
  --volume wordpress_data:/bitnami \
  bitnami/wordpress:latest

Access your application at http://your-ip/

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a volume at the /bitnami path. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define docker volumes namely mariadb_data and wordpress_data. The Wordpress application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

The following docker-compose.yml template demonstrates the use of host directories as data volumes.

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - MARIADB_USER=bn_wordpress
      - MARIADB_DATABASE=bitnami_wordpress
    volumes:
      - /path/to/mariadb-persistence:/bitnami
  wordpress:
    image: bitnami/wordpress:latest
    depends_on:
      - mariadb
    ports:
      - '80:80'
      - '443:443'
    environment:
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - /path/to/wordpress-persistence:/bitnami

1. Create a network (if it does not exist)

$ docker network create wordpress-tier

2. Create a MariaDB container with host volume

$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_wordpress \
  -e MARIADB_DATABASE=bitnami_wordpress \
  --net wordpress-tier \
  --volume /path/to/mariadb-persistence:/bitnami \
  bitnami/mariadb:latest

3. Create the WordPress the container with host volumes

$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e WORDPRESS_DATABASE_USER=bn_wordpress \
  -e WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --net wordpress-tier \
  --volume /path/to/wordpress-persistence:/bitnami \
  bitnami/wordpress:latest

Bitnami provides up-to-date versions of MariaDB and WordPress, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the WordPress container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image

The bitnami/wordpress:latest tag always points to the most recent release. To get the most recent release you can simple repull the latest tag from the Docker Hub with docker pull bitnami/wordpress:latest. However it is recommended to use tagged versions.

1. Get the updated images:

$ docker pull bitnami/wordpress:latest

2. Stop your container

• For docker-compose: $ docker-compose stop wordpress
• For manual execution: $ docker stop wordpress

3. Take a snapshot of the application state

$ rsync -a /path/to/wordpress-persistence /path/to/wordpress-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MariaDB data

You can use these snapshots to restore the application state should the upgrade fail.

4. Remove the stopped container

• For docker-compose: $ docker-compose rm wordpress
• For manual execution: $ docker rm wordpress

5. Run the new image

• For docker-compose: $ docker-compose up wordpress
• For manual execution (mount the directories if needed): docker run --name wordpress bitnami/wordpress:latest

The WordPress instance can be customized by specifying environment variables on the first run. The following environment values are provided to custom WordPress:

• WORDPRESS_USERNAME: WordPress application username. Default: user
• WORDPRESS_PASSWORD: WordPress application password. Default: bitnami
• WORDPRESS_EMAIL: WordPress application email. Default: [email protected]
• WORDPRESS_FIRST_NAME: WordPress user first name. Default: FirstName
• WORDPRESS_LAST_NAME: WordPress user last name. Default: LastName
• WORDPRESS_BLOG_NAME: WordPress blog name. Default: User's blog
• WORDPRESS_HTACESS_OVERRIDE_NONE: Set the Apache AllowOverride variable to None. All the default directives will be loaded from /opt/bitnami/wordpress/wordpress-htaccess.conf. Default: yes.

• MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
• MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
• WORDPRESS_DATABASE_NAME: Database name that WordPress will use to connect with the database. Default: bitnami_wordpress
• WORDPRESS_TABLE_PREFIX: Table prefix to use in WordPress. Default: wp_
• WORDPRESS_DATABASE_USER: Database user that WordPress will use to connect with the database. Default: bn_wordpress
• WORDPRESS_DATABASE_PASSWORD: Database password that WordPress will use to connect with the database. No defaults.
• WORDPRESS_SKIP_INSTALL: Force the container to not execute the WordPress installation wizard. This is necessary in case you use a database that already has WordPress data. Default: no
• ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

• MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
• MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
• MARIADB_ROOT_USER: Database admin user. Default: root
• MARIADB_ROOT_PASSWORD: Database password for the MARIADB_ROOT_USER user. No defaults.
• MYSQL_CLIENT_CREATE_DATABASE_NAME: New database to be created by the mysql client module. No defaults.
• WORDPRESS_TABLE_PREFIX: Table prefix to use in WordPress. Default: wp_
• MYSQL_CLIENT_CREATE_DATABASE_USER: New database user to be created by the mysql client module. No defaults.
• MYSQL_CLIENT_CREATE_DATABASE_PASSWORD: Database password for the MYSQL_CLIENT_CREATE_DATABASE_USER user. No defaults.
• ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - MARIADB_USER=bn_wordpress
      - MARIADB_DATABASE=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - mariadb_data:/bitnami
  wordpress:
    image: bitnami/wordpress:latest
    depends_on:
      - mariadb
    ports:
      - '80:80'
      - '443:443'
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - wordpress_data:/bitnami

volumes:
  mariadb_data:
    driver: local
  wordpress_data:
    driver: local

$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  --net wordpress-tier \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e WORDPRESS_DATABASE_USER=bn_wordpress \
  -e WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  -e WORDPRESS_PASSWORD=my_password \
  --volume wordpress_data:/bitnami \
  bitnami/wordpress:latest

To configure WordPress to send email using SMTP you can set the following environment variables:

• SMTP_HOST: Host for outgoing SMTP email. No defaults.
• SMTP_PORT: Port for outgoing SMTP email. No defaults.
• SMTP_USER: User of SMTP used for authentication (likely email). No defaults.
• SMTP_PASSWORD: Password for SMTP. No defaults.
• SMTP_PROTOCOL: Secure connection protocol to use for SMTP [tls, ssl, none]. No defaults.

This would be an example of SMTP configuration using a GMail account:

• docker-compose (application part):

  wordpress:
    image: bitnami/wordpress:latest
    ports:
      - 80:80
      - 443:443
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - SMTP_HOST=smtp.gmail.com
      - SMTP_PORT=587
      - [email protected]
      - SMTP_PASSWORD=your_password
      - SMTP_PROTOCOL=tls
    volumes:
      - wordpress_data:/bitnami/wordpress

• For manual execution:

$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  --net wordpress-tier \
  --env SMTP_HOST=smtp.gmail.com --env SMTP_PORT=587 \
  --env [email protected] --env SMTP_PASSWORD=your_password \
  --env ALLOW_EMPTY_PASSWORD=yes --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --volume wordpress_data:/bitnami/wordpress \
  bitnami/wordpress:latest

The Bitnami WordPress container supports connecting the WordPress application to an external database. In order to configure it, you should set the following environment variables:

• MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
• MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
• WORDPRESS_DATABASE_NAME: Database name that WordPress will use to connect with the database. Default: bitnami_wordpress
• WORDPRESS_DATABASE_USER: Database user that WordPress will use to connect with the database. Default: bn_wordpress
• WORDPRESS_DATABASE_PASSWORD: Database password that WordPress will use to connect with the database. No defaults.

This would be an example of using an external database for WordPress.

• docker-compose:

  wordpress:
    image: bitnami/wordpress:latest
    ports:
      - 80:80
      - 443:443
    environment:
      - MARIADB_HOST=mariadb_host
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_NAME=wordpress_db
      - WORDPRESS_DATABASE_USER=wordpress_user
      - WORDPRESS_DATABASE_PASSWORD=wordpress_password
    volumes:
      - wordpress_data:/bitnami

• For manual execution:

$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  --net wordpress-tier \
  --env MARIADB_HOST=mariadb_host \
  --env MARIADB_PORT_NUMBER=3306 \
  --env WORDPRESS_DATABASE_NAME=wordpress_db \
  --env WORDPRESS_DATABASE_USER=wordpress_user \
  --env WORDPRESS_DATABASE_PASSWORD=wordpress_password \
  --volume wordpress_data:/bitnami \
  bitnami/wordpress:latest

In case the database already contains data from a previous WordPress installation, you need to set the variable WORDPRESS_SKIP_INSTALL to yes. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. Note that, when setting WORDPRESS_SKIP_INSTALL to yes, the values WORDPRESS_USERNAME, WORDPRESS_PASSWORD, WORDPRESS_BLOG_NAME, WORDPRESS_EMAIL, WORDPRESS_BLOG_NAME and WORDPRESS_SMTP_* variables will be ignored. Make sure that, in this imported database, the table prefix matches the one set in WORDPRESS_TABLE_PREFIX.

The Bitnami WordPress container includes the command line interface wp-cli that can help you to manage and interact with your WP sites. To run this tool, please note you need use the proper system user, daemon.

This would be an example of using wp-cli to display the help menu:

• Using docker-compose command:

$ docker-compose exec wordpress sudo -u daemon -- wp help

• Using docker command:

$ docker exec wordpress sudo -u daemon -- wp help

Find more information about parameters available in the tool in the official documentation.

• Users reported that they wanted to import their WordPress database from other installations, such as this ticket. Now, in order to cover this use case, the variable WORDPRESS_SKIP_INSTALL can be set to avoid the container launch the WordPress installation wizard.

• For performance and security reasons, Apache will set the AllowOverride directive to None by default. This means that, instead of using .htaccess files, all the default directives will be moved to the /opt/bitnami/wordpress/wordpress-htaccess.conf file. The only downside of this is the compatibility with certain plugins, which would require changes in that file (you would need to mount a modified version of wordpress-htaccess.conf compatible with these plugins). If you want to have the default .htaccess behavior, set the WORDPRESS_HTACCESS_OVERRIDE_NONE env var to no.

• wp-cli tool is included in the Docker image. Find it at /opt/bitnami/wp-cli/bin/wp.

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version ($ docker version)
• Output of $ docker info
• Version of this container ($ echo $BITNAMI_IMAGE_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright 2015-2019 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.