public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/wordpress] Release 6.9.2-debian-12-r0 (#91476) 

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-03-10 18:29:24 +01:00 committed by GitHub
parent 8eb703ed53
commit 6aa0b4d4a2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
bitnami/wordpress/6/debian-12/Dockerfile
View File

@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-03-03T07:46:32Z" \
org.opencontainers.image.created="2026-03-10T16:59:11Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/wordpress/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/wordpress" \
org.opencontainers.image.title="wordpress" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="6.9.1"
org.opencontainers.image.version="6.9.2"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@ -28,13 +28,13 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"render-template-1.0.9-162-linux-${OS_ARCH}-debian-12" \
"php-8.4.18-7-linux-${OS_ARCH}-debian-12" \
"render-template-1.0.9-163-linux-${OS_ARCH}-debian-12" \
"php-8.4.18-8-linux-${OS_ARCH}-debian-12" \
"apache-2.4.66-1-linux-${OS_ARCH}-debian-12" \
"mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \
"postgresql-lib-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"libphp-8.4.18-5-linux-${OS_ARCH}-debian-12" \
"wordpress-6.9.1-1-linux-${OS_ARCH}-debian-12" \
"wordpress-6.9.2-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -59,11 +59,11 @@ RUN /opt/bitnami/scripts/apache-modphp/postunpack.sh
RUN /opt/bitnami/scripts/wordpress/postunpack.sh
ENV APACHE_HTTPS_PORT_NUMBER="" \
APACHE_HTTP_PORT_NUMBER="" \
APP_VERSION="6.9.1" \
APP_VERSION="6.9.2" \
BITNAMI_APP_NAME="wordpress" \
IMAGE_REVISION="8" \
IMAGE_REVISION="0" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
PATH="/opt/bitnami/wp-cli/bin:/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/apache/bin:/opt/bitnami/mysql/bin:/opt/bitnami/postgresql-lib/bin:$PATH"
PATH="/opt/bitnami/wp-cli/bin:/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/apache/bin:/opt/bitnami/mysql/bin:$PATH"
EXPOSE 8080 8443

44
bitnami/wordpress/README.md
View File

@ -5,7 +5,7 @@
[Overview of WordPress](https://wordpress.org)
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.
## <a id="tl-dr"></a> TL;DR
## TL;DR
```console
docker run --name wordpress bitnami/wordpress:latest
@ -13,7 +13,7 @@ docker run --name wordpress 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](#environment-variables) section for a more secure deployment.
## <a id="why-use-bitnami-secure-images"></a> Why use Bitnami Secure Images?
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@ -30,15 +30,15 @@ Each image comes with valuable security metadata. You can view the metadata in [
If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
## <a id="deploy-kubernetes"></a> How to deploy WordPress in Kubernetes
## 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](https://github.com/bitnami/charts/tree/master/bitnami/wordpress).
## <a id="why-non-root"></a> Why use a non-root container?
## 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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
## 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](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
@ -46,7 +46,7 @@ You can see the equivalence between the different tags by taking a look at the `
Subscribe to project updates by watching the [bitnami/containers GitHub repository](https://github.com/bitnami/containers).
## <a id="get-this-image"></a> Get this image
## Get this image
The recommended way to get the Bitnami WordPress Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/wordpress).
@ -68,11 +68,11 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## <a id="how-to-use"></a> How to use this image
## How to use this image
WordPress requires access to a MySQL or MariaDB database to store information. We'll use the [Bitnami Docker Image for MariaDB](https://github.com/bitnami/containers/tree/main/bitnami/mariadb) for the database requirements.
## <a id="persisting"></a> Persisting your application
## 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.
@ -82,11 +82,11 @@ To avoid inadvertent removal of volumes, you can [mount host directories as data
> **NOTE** Because this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## <a id="configuration"></a> Configuration
## Configuration
The following section describes environment variables and FIPS configuration.
### <a id="environment-variables"></a> Environment variables
### Environment variables
The following tables list the main variables you can set.
@ -169,7 +169,7 @@ The following tables list the main variables you can set.
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.
### <a id="examples"></a> Examples
### Examples
The following examples show SMTP configuration and connecting to an existing database.
@ -181,13 +181,13 @@ The `WORDPRESS_SMTP_*` environment variables allows you configure the SMTP setti
The Bitnami WordPress container supports connecting the WordPress application to an external database. 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`.
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
### FIPS configuration in Bitnami Secure Images
The Bitnami WordPress Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
## <a id="wp-cli"></a> WP-CLI tool
## 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**.
@ -207,7 +207,7 @@ docker exec wordpress wp help
Find more information about parameters available in the tool in the [official documentation](https://make.wordpress.org/cli/handbook/config/).
## <a id="logging"></a> Logging
## Logging
The Bitnami WordPress Docker image sends the container logs to `stdout`. To view the logs:
@ -223,11 +223,11 @@ docker-compose logs wordpress
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## <a id="maintenance"></a> Maintenance
## Maintenance
The following sections describe how to back up, restore, and upgrade the container.
### <a id="backing-up"></a> Backing up your container
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
@ -252,7 +252,7 @@ To backup your data, configuration and logs, follow these simple steps:
cp -a /bitnami/wordpress /backups/latest
```
### <a id="restoring-backup"></a> Restoring a backup
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
@ -276,11 +276,11 @@ For the WordPress container:
bitnami/wordpress:latest
```
## <a id="customize"></a> Customize this image
## 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.
### <a id="extend-image"></a> Extend this image
### Extend this image
Before extending this image, please note there are certain configuration settings you can modify using the original image:
@ -297,7 +297,7 @@ FROM bitnami/wordpress
...
```
## <a id="notable-changes"></a> Notable changes
## Notable changes
The following subsections describe notable changes.
@ -326,7 +326,7 @@ The following subsections describe notable changes.
### 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](#customize) section for more information.
- This image has been adapted so it's easier to customize. See the [Customize this image](#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`.
@ -343,7 +343,7 @@ The following subsections describe notable changes.
- **wp-cli** tool is included in the Docker image. Find it at **/opt/bitnami/wp-cli/bin/wp**.
## <a id="license"></a> License
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.