bitnami/wordpress

Bitnami Secure Image for WordPress

WordPress is the world's most popular blogging and content management platform. Powerful yet simple, everyone from students to global corporations use it to build beautiful, functional websites.

Overview of WordPress Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

console
docker run --name wordpress REGISTRY_NAME/bitnami/wordpress:latest

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

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 https://github.com/bitnami/charts/tree/master/bitnami/wordpress.

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.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the https://github.com/bitnami/containers.

Get this image

The recommended way to get the Bitnami WordPress Docker Image is to pull the prebuilt image from the https://hub.docker.com/r/bitnami/wordpress.

console
docker pull REGISTRY_NAME/bitnami/wordpress:latest

To use a specific version, you can pull a versioned tag. You can view the https://hub.docker.com/r/bitnami/wordpress/tags/ in the Docker Hub Registry.

console
docker pull REGISTRY_NAME/bitnami/wordpress:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

console
git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t REGISTRY_NAME/bitnami/APP:latest .

How to use this image

WordPress requires access to a MySQL or MariaDB database to store information. We'll use the https://github.com/bitnami/containers/tree/main/bitnami/mariadb for the database requirements.

Persisting your application

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 https://github.com/bitnami/containers/blob/main/bitnami/mariadb#persisting-your-database.

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.

NOTE Because this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Configuration

The following section describes environment variables and FIPS configuration.

Environment variables

The following tables list the main variables you can set.

Customizable environment variables

Read-only environment variables

| Name | Description | Value

_Note: the README for this container is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at [***]