[bitnami/wordpress-nginx] Release 6.9.4-debian-12-r5 (#92473)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-04-15 11:29:06 +02:00 committed by GitHub
parent bf5ed61f2a
commit 978eb0969c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 12 additions and 79 deletions

View File

@ -7,7 +7,7 @@ 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-04-08T22:06:56Z" \
org.opencontainers.image.created="2026-04-15T09:14:30Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/wordpress-nginx/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/wordpress-nginx" \
@ -29,8 +29,8 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"render-template-1.0.9-164-linux-${OS_ARCH}-debian-12" \
"php-8.4.19-1-linux-${OS_ARCH}-debian-12" \
"nginx-1.29.8-0-linux-${OS_ARCH}-debian-12" \
"php-8.4.20-2-linux-${OS_ARCH}-debian-12" \
"nginx-1.30.0-0-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" \
"wordpress-nginx-6.9.4-0-linux-${OS_ARCH}-debian-12" \
@ -58,7 +58,7 @@ RUN /opt/bitnami/scripts/nginx-php-fpm/postunpack.sh
RUN /opt/bitnami/scripts/wordpress/postunpack.sh
ENV APP_VERSION="6.9.4" \
BITNAMI_APP_NAME="wordpress-nginx" \
IMAGE_REVISION="4" \
IMAGE_REVISION="5" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
NGINX_HTTPS_PORT_NUMBER="" \
NGINX_HTTP_PORT_NUMBER="" \

View File

@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name wordpress-nginx bitnami/wordpress-nginx:latest
```
**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](#environment-variables) section for a more secure deployment.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/wordpress-nginx/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/wordpress-nginx/docker-compose.yml)
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/wordpress).
## Why use Bitnami Secure Images?
@ -147,8 +153,6 @@ The following tables list the main variables you can set.
| `WP_CLI_DAEMON_USER` | WP-CLI system user. | `daemon` |
| `WP_CLI_DAEMON_GROUP` | WP-CLI system group. | `daemon` |
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.
### Examples
#### SMTP configuration
@ -173,14 +177,6 @@ The Bitnami WordPress container includes the command line interface **wp-cli** t
This would be an example of using **wp-cli** to display the help menu:
- Using `docker-compose` command:
```console
docker-compose exec wordpress wp help
```
- Using `docker` command:
```console
docker exec wordpress wp help
```
@ -189,70 +185,7 @@ Find more information about parameters available in the tool in the [official do
## Logging
The Bitnami WordPress Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs wordpress
```
Or using Docker Compose:
```console
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.
## Maintenance
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
#### Step 1: Stop the currently running container
```console
docker stop wordpress
```
Or using Docker Compose:
```console
docker-compose stop wordpress
```
#### Step 2: Run the backup command
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.
```console
docker run --rm -v /path/to/wordpress-backups:/backups --volumes-from wordpress busybox \
cp -a /bitnami/wordpress /backups/latest
```
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
```diff
$ 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:
```diff
$ docker run -d --name wordpress \
...
- --volume /path/to/wordpress-persistence:/bitnami/wordpress \
+ --volume /path/to/wordpress-backups/latest:/bitnami/wordpress \
bitnami/wordpress:latest
```
The Bitnami WordPress with NGINX Docker image sends the container logs to the `stdout`. 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.
## Customize this image