bjoerrrrn/wordpress repository overview

⁠Fork of wordpress container

This was a Fork of the awesome bitnami/wordpress container. I rebased to the offical wordpress docker container. I just added php-redis module, activated imagick and raised the upload limits.

⁠What is WordPress?

https://www.wordpress.org/⁠

⁠TL;DR;

⁠Docker Compose

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

⁠Why use Bitnami Images?

• 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.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC)⁠. You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released daily with the latest distribution packages available.

⁠How to deploy WordPress in Kubernetes?

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.

⁠Why use a non-root container?

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs⁠.

⁠Supported tags and respective Dockerfile links

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

• 5-debian-10, 5.4.0-debian-10-r18, 5, 5.4.0, latest (5/debian-10/Dockerfile)⁠

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

⁠Prerequisites

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

⁠How to use this image

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

⁠Run the application using Docker Compose

The main folder of this repository contains a functional docker-compose.yml⁠ file. Run the application using it as shown below:

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

⁠Using the Docker Command Line

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

⁠Step 1: Create a network

$ docker network create wordpress-network

⁠Step 2: Create a volume for MariaDB persistence and create a MariaDB container

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

⁠Step 3: Create volumes for WordPress persistence and launch the container

$ docker volume create --name wordpress_data
$ docker run -d --name wordpress \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --network wordpress-network \
  --volume wordpress_data:/bitnami/wordpress \
  bitnami/wordpress:latest

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

⁠Persisting your application

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/wordpress 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.

⁠Mount host directories as data volumes with Docker Compose

This requires a minor change to the docker-compose.yml⁠ file present in this repository:

 ...
 services:
   mariadb:
     ...
     volumes:
-      - 'mariadb_data:/bitnami/mariadb'
+      - /path/to/mariadb-persistence:/bitnami/mariadb
   ...
   wordpress:
      ...
     volumes:
-      - 'wordpress_data:/bitnami/wordpress
+      - /path/to/wordpress-persistence:/bitnami/wordpress
   ...
-volumes:
-  mariadb_data:
-    driver: local
-  wordpress_data:
-    driver: local

⁠Mount host directories as data volumes using the Docker command line

⁠Step 1: Create a network (if it does not exist)

$ docker network create wordpress-network

⁠Step 2. Create a MariaDB container with host volume

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

⁠Step 3. Create the WordPress the container with host volumes

$ docker run -d --name wordpress \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --network wordpress-network \
  --volume /path/to/wordpress-persistence:/bitnami/wordpress \
  bitnami/wordpress:latest

⁠Upgrading WordPress

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⁠.

⁠Step 1. Get the updated images:

$ docker pull bitnami/wordpress:latest

⁠Step 2. Stop your container

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

⁠Step 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.

⁠Step 4. Remove the stopped container

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

⁠Step 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

⁠Configuration

⁠Environment variables

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

⁠User and Site configuration

• 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_SCHEME: Scheme to generate application URLs. Default: http
• WORDPRESS_HTACCESS_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.

⁠Use an existing database

• 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

⁠Create a database for WordPress using mysql-client

• 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

⁠PHP configuration

• PHP_MEMORY_LIMIT: Memory limit for PHP. Default: 256M

⁠Specifying Environment variables using Docker Compose

This requires a minor change to the docker-compose.yml⁠ file present in this repository:

services:
  mariadb:
  ...
    environment:
      - MARIADB_USER=bn_wordpress
      - MARIADB_DATABASE=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
  ...
  wordpress:
  ...
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
  ...

⁠Specifying Environment variables on the Docker command line

$ docker run -d --name wordpress \
  -p 8080:8080 -p 8443:8443 \
  --network wordpress-network \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --env WORDPRESS_PASSWORD=my_password \
  --volume wordpress_data:/bitnami/wordpresss \
  bitnami/wordpress:latest

⁠SMTP Configuration

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:

• Modify the docker-compose.yml⁠ file present in this repository:

   wordpress:
     ...
     environment:
       - MARIADB_HOST=mariadb
       - MARIADB_PORT_NUMBER=3306
       - WORDPRESS_DATABASE_USER=bn_wordpress
       - WORDPRESS_DATABASE_NAME=bitnami_wordpress
       - ALLOW_EMPTY_PASSWORD=yes
+      - SMTP_HOST=smtp.gmail.com
+      - SMTP_PORT=587
+      - [email protected]
+      - SMTP_PASSWORD=your_password
+      - SMTP_PROTOCOL=tls
    ...

• For manual execution:

$ docker run -d --name wordpress \
  -p 8080:8080 -p 8443:8443 \
  --network wordpress-network \
  --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

⁠Connect WordPress docker container to an existing database

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.
• WORDPRESS_DATABASE_SSL_CA_FILE: Certificate to connect with the database using SSL. No defaults.

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

• Modify the docker-compose.yml⁠ file present in this repository:

   wordpress:
     ...
     environment:
-      - MARIADB_HOST=mariadb
+      - MARIADB_HOST=mariadb_host
       - MARIADB_PORT_NUMBER=3306
       - WORDPRESS_DATABASE_NAME=wordpress_db
       - WORDPRESS_DATABASE_USER=wordpress_user
-      - ALLOW_EMPTY_PASSWORD=yes
+      - WORDPRESS_DATABASE_PASSWORD=wordpress_password
     ...

• For manual execution:

$ docker run -d --name wordpress\
  -p 8080:8080 -p 8443:8443 \
  --network wordpress-network \
  --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/wordpress \
  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.

⁠WP-CLI tool

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 wp help

• Using docker command:

$ docker exec wordpress wp help

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

⁠Customize this image

The Bitnami WordPress Docker image is designed to be extended so it can be used as the base image for your custom web applications.

⁠Extend this image

Before extending this image, please note there are certain configuration settings you can modify using the original image:

• Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables APACHE_HTTP_PORT_NUMBER and APACHE_HTTPS_PORT_NUMBER respectively.
• Adding custom virtual hosts⁠.
• Replacing the 'httpd.conf' file⁠.
• Using custom SSL certificates⁠.

If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:

FROM bitnami/wordpress
## Put your customizations below
...

Here is an example of extending the image with the following modifications:

• Install the vim editor
• Modify the Apache configuration file
• Modify the ports used by Apache

FROM bitnami/wordpress
LABEL maintainer "Bitnami <[email protected]>"

## Install 'vim'
USER 0 # Required to perform privileged actions
RUN install_packages vim
USER 1001 # Revert to the original non-root user

## Enable mod_ratelimit module
RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf

## Modify the ports used by Apache by default
# It is also possible to change these environment variables at runtime
ENV APACHE_HTTP_PORT_NUMBER=8181
ENV APACHE_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143

Based on the extended image, you can use a Docker Compose file like the one below to add other features:

version: '2'
services:
  mariadb:
    image: 'bitnami/mariadb:10.3'
    volumes:
      - 'mariadb_data:/bitnami'
    environment:
      - MARIADB_USER=bn_wordpress
      - MARIADB_DATABASE=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
  wordpress:
    build: .
    ports:
      - '80:8181'
      - '443:8143'
    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

⁠Notable Changes

⁠5.3.2-debian-10-r30

• The WordPress container has been migrated to a "non-root" user approach. Previously the container ran as the root user and the Apache daemon was started as the daemon user. From now on, both the container and the Apache daemon run as user 1001. You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.
• Consequences:
  • The HTTP/HTTPS ports exposed by the container are now 8080/8443 instead of 80/443.
  • Backwards compatibility is not guaranteed when data is persisted using docker or docker-compose. We highly recommend migrating the WP site by exporting its content, and importing it on a new WordPress container. In the links below you'll find some alternatives:
    • Migrate WordPress using All-in-One WP Migration plugin⁠
    • Migrate WordPress using VaultPress⁠
  • No writing permissions will be granted on wp-config.php by default.

⁠5.2.1-debian-9-r9 and 5.2.1-ol-7-r9

• This image has been adapted so it's easier to customize. See the Customize this image⁠ section for more information.
• The Apache configuration volume (/bitnami/apache) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the Apache configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom Apache configuration files are advised to mount a volume for the configuration at /opt/bitnami/apache/conf, or mount specific configuration files individually.
• The PHP configuration volume (/bitnami/php) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at /opt/bitnami/php/conf, or mount specific configuration files individually.
• Enabling custom Apache certificates by placing them at /opt/bitnami/apache/certs has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at /certs.

⁠5.1.1-r28, 5.1.1-rhel-7-r31 and 5.1.1-ol-7-r30

• 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.

⁠5.0.3-r20

• 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.

⁠5.0.0-r0

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

⁠Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue⁠, or submit a [pull request](https://github.com/bitnami/bitnami-docker-wordpress/⁠