Bitnami Docker Image for WordPress with NGINX
In order to unify the approaches followed for Bitnami containers and Bitnami Helm charts, we are moving the different bitnami/bitnami-docker-<container>
repositories to a single monorepo bitnami/containers
. Please follow bitnami/containers to keep you updated about the latest Bitnami images.
More information here: https://blog.bitnami.com/2022/07/new-source-of-truth-bitnami-containers.html
WordPress with NGINX combines the most popular blogging application with the power of the NGINX web server.
Overview of WordPress with NGINX
$ curl -LO https://raw.githubusercontent.com/bitnami/bitnami-docker-wordpress-nginx/master/docker-compose.yml
$ docker-compose up
Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables section for a more secure deployment.
DOCKER_CONTENT_TRUST=1
to verify the integrity of the images.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.
Dockerfile
linksLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
Subscribe to project updates by watching the bitnami/wordpress-nginx GitHub repo.
The recommended way to get the Bitnami WordPress with NGINX Docker Image is to pull the prebuilt image from the Docker Hub Registry.
$ docker pull bitnami/wordpress-nginx:latest
To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
$ docker pull bitnami/wordpress-nginx:[TAG]
If you wish, you can also build the image yourself.
$ docker build -t bitnami/wordpress-nginx:latest 'https://github.com/bitnami/bitnami-docker-wordpress-nginx.git#master:6/debian-11'
WordPress requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.
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
If you want to run the application manually instead of using docker-compose
, these are the basic steps you need to run:
$ docker network create wordpress-network
$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_wordpress \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_wordpress \
--network wordpress-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
$ 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_PASSWORD=bitnami \
--env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
--network wordpress-network \
--volume wordpress_data:/bitnami/wordpress \
bitnami/wordpress-nginx:latest
Access your application at http://your-ip/
If you remove the container all your data 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 directory at the /bitnami/wordpress
path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the MariaDB data.
The above examples define the Docker volumes named mariadb_data
and wordpress_data
. The WordPress application state will persist as long as volumes are not removed.
To avoid inadvertent removal of volumes, you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.
This requires a minor change to the docker-compose.yml
file present in this repository:
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
NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001
.
$ docker network create wordpress-network
$ docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_wordpress \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_wordpress \
--network wordpress-network \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001
.
$ 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_PASSWORD=bitnami \
--env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
--network wordpress-network \
--volume /path/to/wordpress-persistence:/bitnami/wordpress \
bitnami/wordpress-nginx:latest
NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001
.
When you start the WordPress image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run
command line. If you want to add a new environment variable:
For docker-compose add the variable name and value under the application section in the docker-compose.yml
file present in this repository:
wordpress:
...
environment:
- WORDPRESS_PASSWORD=my_password
...
For manual execution add a --env
option with each variable and value:
$ docker run -d --name wordpress -p 80:8080 -p 443:8443 \
--env WORDPRESS_PASSWORD=my_password \
--network wordpress-tier \
--volume /path/to/wordpress-persistence:/bitnami \
bitnami/wordpress-nginx:latest
Available environment variables:
NGINX_HTTP_PORT_NUMBER
: Port used by NGINX for HTTP. Default: 8080
NGINX_HTTPS_PORT_NUMBER
: Port used by NGINX for HTTPS. Default: 8443
NGINX_ENABLE_ABSOLUTE_REDIRECT
: Use absolute URLs in Location header in redirections. Default: no
NGINX_ENABLE_PORT_IN_REDIRECT
: Use listening port in redirections issued by NGINX. Default: no
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_DATA_TO_PERSIST
: Space separated list of files and directories to persist. Use a space to persist no data: " "
. Default: "wp-config.php wp-content"
WORDPRESS_RESET_DATA_PERMISSIONS
: Force resetting ownership/permissions on persisted data when restarting WordPress, otherwise it assumes the ownership/permissions are correct. Ignored when running WP as non-root. Default: no
WORDPRESS_TABLE_PREFIX
: Table prefix to use in WordPress. Default: wp_
WORDPRESS_PLUGINS
: List of WordPress plugins to install and activate, separated via commas. Can also be set to all
to activate all currently installed plugins, or none
to skip. Default: none
WORDPRESS_EXTRA_INSTALL_ARGS
: Extra flags to append to the WordPress 'wp core install' command call. No defaults.WORDPRESS_EXTRA_CLI_ARGS
: Extra flags to append to all WP-CLI command calls. No defaults.WORDPRESS_EXTRA_WP_CONFIG_CONTENT
: Extra configuration to append to wp-config.php during install. No defaults.WORDPRESS_ENABLE_HTTPS
: Whether to use HTTPS by default. Default: no
WORDPRESS_SKIP_BOOTSTRAP
: Skip the WordPress installation wizard. This is necessary when providing a database with existing WordPress data. Default: no
WORDPRESS_AUTO_UPDATE_LEVEL
: Level of auto-updates to allow for the WordPress core installation. Valid values: major
, minor
, none
. Default: none
WORDPRESS_ENABLE_REVERSE_PROXY
: Enable WordPress support for reverse proxy headers. Default: no
WORDPRESS_ENABLE_MULTISITE
: Enable WordPress Multisite configuration. Default: no
WORDPRESS_MULTISITE_HOST
: WordPress hostname/address. Only used for Multisite installations. No defaults.WORDPRESS_MULTISITE_EXTERNAL_HTTP_PORT_NUMBER
: Port to used by WordPress to generate URLs and links when accessing using HTTP. Will be ignored if multisite mode is not enabled. Default 80
WORDPRESS_MULTISITE_EXTERNAL_HTTPS_PORT_NUMBER
: Port to used by WordPress to generate URLs and links when accessing using HTTPS. Will be ignored if multisite mode is not enabled. Default 443
WORDPRESS_MULTISITE_NETWORK_TYPE
: WordPress Multisite network type to enable. Valid values: subfolder
, subdirectory
, subdomain
. Default: subdomain
WORDPRESS_MULTISITE_ENABLE_NIP_IO_REDIRECTION
: Whether to enable IP address redirection to nip.io wildcard DNS when enabling WordPress Multisite. This is useful when running on an IP address with subdomain network type. Default: no
WORDPRESS_MULTISITE_FILEUPLOAD_MAXK
: Maximum upload file size allowed for WordPress Multisite uploads, in kilobytes. Default: 81920
WORDPRESS_DATABASE_HOST
: Hostname for the MariaDB or MySQL server. Default: mariadb
WORDPRESS_DATABASE_PORT_NUMBER
: Port used by the MariaDB or MySQL 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_ENABLE_DATABASE_SSL
: Whether to enable SSL for database connections. Default: no
WORDPRESS_VERIFY_DATABASE_SSL
: Whether to verify the database SSL certificate when SSL is enabled for database connections. Default: yes
WORDPRESS_DATABASE_SSL_CERT_FILE
: Path to the database client certificate file. No defaultsWORDPRESS_DATABASE_SSL_KEY_FILE
: Path to the database client certificate key file. No defaultsWORDPRESS_DATABASE_SSL_CA_FILE
: Path to the database server CA bundle file. No defaultsALLOW_EMPTY_PASSWORD
: It can be used to allow blank passwords. Default: no
MYSQL_CLIENT_FLAVOR
: SQL database flavor. Valid values: mariadb
or mysql
. Default: mariadb
MYSQL_CLIENT_DATABASE_HOST
: Hostname for the MariaDB or MySQL server. Default: mariadb
MYSQL_CLIENT_DATABASE_PORT_NUMBER
: Port used by the MariaDB or MySQL server. Default: 3306
MYSQL_CLIENT_DATABASE_ROOT_USER
: Database admin user. Default: root
MYSQL_CLIENT_DATABASE_ROOT_PASSWORD
: Database password for the database admin user. No defaults.MYSQL_CLIENT_CREATE_DATABASE_NAME
: New database to be created by the mysql client module. No defaults.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.MYSQL_CLIENT_CREATE_DATABASE_CHARACTER_SET
: Character set to use for the new database. No defaults.MYSQL_CLIENT_CREATE_DATABASE_COLLATE
: Database collation to use for the new database. No defaults.MYSQL_CLIENT_ENABLE_SSL_WRAPPER
: Whether to force SSL connections to the database via the mysql
CLI tool. Useful for applications that rely on the CLI instead of APIs. Default: no
MYSQL_CLIENT_ENABLE_SSL
: Whether to force SSL connections for the database. Default: no
MYSQL_CLIENT_SSL_CA_FILE
: Path to the SSL CA file for the new database. No defaultsMYSQL_CLIENT_SSL_CERT_FILE
: Path to the SSL CA file for the new database. No defaultsMYSQL_CLIENT_SSL_KEY_FILE
: Path to the SSL CA file for the new database. No defaultsALLOW_EMPTY_PASSWORD
: It can be used to allow blank passwords. Default: no
To configure WordPress to send email using SMTP you can set the following environment variables:
WORDPRESS_SMTP_HOST
: SMTP host.WORDPRESS_SMTP_PORT
: SMTP port.WORDPRESS_SMTP_USER
: SMTP account user.WORDPRESS_SMTP_PASSWORD
: SMTP account password.PHP_ENABLE_OPCACHE
: Enable OPcache for PHP scripts. Default: yes
PHP_EXPOSE_PHP
: Enables HTTP header with PHP version. No default.PHP_MAX_EXECUTION_TIME
: Maximum execution time for PHP scripts. No default.PHP_MAX_INPUT_TIME
: Maximum input time for PHP scripts. No default.PHP_MAX_INPUT_VARS
: Maximum amount of input variables for PHP scripts. No default.PHP_MEMORY_LIMIT
: Memory limit for PHP scripts. Default: 256M
PHP_POST_MAX_SIZE
: Maximum size for PHP POST requests. No default.PHP_UPLOAD_MAX_FILESIZE
: Maximum file size for PHP uploads. No default.This would be an example of SMTP configuration using a Gmail account:
Modify the docker-compose.yml
file present in this repository:
wordpress:
...
environment:
- WORDPRESS_DATABASE_USER=bn_wordpress
- WORDPRESS_DATABASE_NAME=bitnami_wordpress
- ALLOW_EMPTY_PASSWORD=yes
- WORDPRESS_SMTP_HOST=smtp.gmail.com
- WORDPRESS_SMTP_PORT=587
- [email protected]
- WORDPRESS_SMTP_PASSWORD=your_password
...
For manual execution:
$ docker run -d --name wordpress -p 80:8080 -p 443:8443 \
--env WORDPRESS_DATABASE_USER=bn_wordpress \
--env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
--env WORDPRESS_SMTP_HOST=smtp.gmail.com \
--env WORDPRESS_SMTP_PORT=587 \
--env [email protected] \
--env WORDPRESS_SMTP_PASSWORD=your_password \
--network wordpress-tier \
--volume /path/to/wordpress-persistence:/bitnami \
bitnami/wordpress-nginx:latest
The Bitnami WordPress container supports connecting the WordPress application to an external database. This would be an example of using an external database for WordPress.
Modify the docker-compose.yml
file present in this repository:
wordpress:
...
environment:
- - WORDPRESS_DATABASE_HOST=mariadb
+ - WORDPRESS_DATABASE_HOST=mariadb_host
- WORDPRESS_DATABASE_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 WORDPRESS_DATABASE_HOST=mariadb_host \
--env WORDPRESS_DATABASE_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-nginx:latest
In case the database already contains data from a previous WordPress installation, you need to set the variable WORDPRESS_SKIP_BOOTSTRAP
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_BOOTSTRAP
to yes
, values for environment variables such as WORDPRESS_USERNAME
, WORDPRESS_PASSWORD
or WORDPRESS_EMAIL
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:
docker-compose
command:$ docker-compose exec wordpress wp help
docker
command:$ docker exec wordpress wp help
Find more information about parameters available in the tool in the official documentation.
The Bitnami WordPress Docker image sends the container logs to stdout
. To view the logs:
$ docker logs wordpress
Or using Docker Compose:
$ docker-compose logs wordpress
You can configure the containers logging driver using the --log-driver
option if you wish to consume the container logs differently. In the default configuration docker uses the json-file
driver.
To backup your data, configuration and logs, follow these simple steps:
$ docker stop wordpress
Or using Docker Compose:
$ docker-compose stop wordpress
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
$ docker run --rm -v /path/to/wordpress-backups:/backups --volumes-from wordpress busybox \
cp -a /bitnami/wordpress /backups/latest
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
$ docker run -d --name mariadb \
...
- --volume /path/to/mariadb-persistence:/bitnami/mariadb \
+ --volume /path/to/mariadb-backups/latest:/bitnami/mariadb \
bitnami/mariadb:latest
For the WordPress container:
$ docker run -d --name wordpress \
...
- --volume /path/to/wordpress-persistence:/bitnami/wordpress \
+ --volume /path/to/wordpress-backups/latest:/bitnami/wordpress \
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-nginx: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-nginx:latest
. However it is recommended to use tagged versions.
$ docker pull bitnami/wordpress-nginx:latest
Stop the currently running container using the command
$ docker-compose stop wordpress
Follow the steps in Backing up your container to take a snapshot of the current application state.
Remove the currently running container by executing the following command:
docker-compose rm -v wordpress
Update the image tag in docker-compose.yml
and re-create your container with the new image:
$ docker-compose up -d
The Bitnami WordPress with NGINX Docker image is designed to be extended so it can be used as the base image for your custom web applications.
Before extending this image, please note there are certain configuration settings you can modify using the original image:
NGINX_HTTP_PORT_NUMBER
and NGINX_HTTPS_PORT_NUMBER
respectively.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-nginx
## Put your customizations below
...
Here is an example of extending the image with the following modifications:
vim
editorFROM bitnami/wordpress-nginx
## Change user to perform privileged actions
USER 0
## Install 'vim'
RUN install_packages vim
## Revert to the original non-root user
USER 1001
## Modify 'worker_connections' on NGINX config file to '512'
RUN sed -i -r "s#(\s+worker_connections\s+)[0-9]+;#\1512;#" /opt/bitnami/nginx/conf/nginx.conf
## Modify the ports used by NGINX by default
# It is also possible to change these environment variables at runtime
ENV NGINX_HTTP_PORT_NUMBER=8181
ENV NGINX_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143
Based on the extended image, you can update the docker-compose.yml
file present in this repository to add other features:
wordpress:
- image: bitnami/wordpress-nginx:latest
+ build: .
ports:
- - '80:8080'
- - '443:8443'
+ - '80:8181'
+ - '443:8143'
environment:
+ - PHP_MEMORY_LIMIT=512m
...
WORDPRESS_ENABLE_MULTISITE
and related environment variables.WORDPRESS_PLUGINS
.WORDPRESS_AUTO_UPDATE_LEVEL
. In addition, auto-updates have been disabled by default. To update WordPress core, we recommend to swap the container image version for your deployment instead of using the built-in update functionality.root
user and the NGINX daemon was started as the daemon
user. From now on, both the container and the NGINX daemon run as user 1001
. You can revert this behavior by changing USER 1001
to USER root
in the Dockerfile.8080/8443
instead of 80/443
.wp-config.php
by default./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./opt/bitnami/nginx/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
.WordPress with NGINX's branch 5.x.x is no longer maintained by upstream and is now internally tagged as to be deprecated. This branch will no longer be released in our catalog a month after this notice is published, but already released container images will still persist in the registries. Valid to be removed starting on: 07-29-2022
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. Be sure to include the following information in your issue:
docker version
)docker info
Please, note this asset is a community-supported solution. This means that the Bitnami team is not actively working on new features/improvements nor providing support through GitHub Issues. Any new issue will stay open for 20 days to allow the community to contribute, after 15 days without activity the issue will be marked as stale being closed after 5 days.
The Bitnami team will review any PR that is created, feel free to create a PR if you find any issue or want to implement a new feature.
New versions and releases cadence are not going to be affected. Once a new version is released in the upstream project, the Bitnami container image will be updated to use the latest version, supporting the different branches supported by the upstream project as usual.
Copyright © 2022 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.