Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-29 16:27:49 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/wordpress-nginx] Release 6.9.1-debian-12-r5 (#91069)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-24 14:02:35 +01:00
committed by GitHub
parent f148eb0102
commit b0eaf0de0e
2 changed files with 9 additions and 280 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
bitnami/wordpress-nginx/6/debian-12/Dockerfile
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-02-18T12:43:11Z" \
org.opencontainers.image.created="2026-02-24T12:40:35Z" \
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" \
@@ -23,7 +23,7 @@ ENV HOME="/" \
COPY prebuildfs /
SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
# Install required system packages and dependencies
RUN install_packages acl ca-certificates curl gettext less libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libexpat1 libffi8 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libgeoip1 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhashkit2 libhogweed6 libicu72 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.5-0 liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpq5 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl3 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libwebp7 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 libzstd1 openssl procps zlib1g
RUN install_packages acl ca-certificates curl gettext less libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libexpat1 libffi8 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libgeoip1 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhashkit2 libhogweed6 libicu72 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.5-0 liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpq5 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl3 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libuuid1 libwebp7 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 libzstd1 openssl procps zlib1g
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 ; \
@@ -32,6 +32,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
"php-8.4.18-1-linux-${OS_ARCH}-debian-12" \
"nginx-1.29.5-0-linux-${OS_ARCH}-debian-12" \
"mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \
"postgresql-lib-18.2.0-0-linux-${OS_ARCH}-debian-12" \
"wordpress-nginx-6.9.1-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
@@ -57,10 +58,11 @@ RUN /opt/bitnami/scripts/nginx-php-fpm/postunpack.sh
RUN /opt/bitnami/scripts/wordpress/postunpack.sh
ENV APP_VERSION="6.9.1" \
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="" \
PATH="/opt/bitnami/wp-cli/bin:/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/nginx/sbin:/opt/bitnami/mysql/bin:$PATH"
PATH="/opt/bitnami/wp-cli/bin:/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/nginx/sbin:/opt/bitnami/mysql/bin:/opt/bitnami/postgresql-lib/bin:$PATH"
EXPOSE 8080 8443

279
bitnami/wordpress-nginx/README.md
View File

@@ -66,56 +66,10 @@ docker build -t bitnami/APP:latest .
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.
### Using the Docker Command Line
#### Step 1: Create a network
```console
docker network create wordpress-network
```
#### Step 2: Create a volume for MariaDB persistence and create a MariaDB container
```console
$ 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
```
#### Step 3: Create volumes for WordPress persistence and launch the container
```console
$ 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/`
### Run the application using Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/wordpress-nginx/docker-compose.yml > docker-compose.yml
docker-compose up
```
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes.
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## 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.
@@ -126,69 +80,6 @@ The above examples define the Docker volumes named `mariadb_data` and `wordpress
To avoid inadvertent removal of volumes, you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). 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`](https://github.com/bitnami/containers/blob/main/bitnami/wordpress-nginx/docker-compose.yml) file present in this repository:
```diff
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`.
### Mount host directories as data volumes using the Docker command line
#### Step 1: Create a network (if it does not exist)
```console
docker network create wordpress-network
```
#### Step 2. Create a MariaDB container with host volume
```console
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`.
#### Step 3. Create the WordPress container with host volumes
```console
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`.
## Configuration
@@ -272,100 +163,18 @@ docker run -d --name wordpress \
| `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. 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`](https://github.com/bitnami/containers/blob/main/bitnami/wordpress-nginx/docker-compose.yml) file present in this repository:
```yaml
wordpress:
...
environment:
- WORDPRESS_PASSWORD=my_password
...
```
- For manual execution add a `--env` option with each variable and value:
```console
$ 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
```
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 using a Gmail account
#### SMTP configuration
This would be an example of SMTP configuration using a Gmail account:
- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/wordpress-nginx/docker-compose.yml) file present in this repository:
```yaml
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
- WORDPRESS_SMTP_USER=your_email@gmail.com
- WORDPRESS_SMTP_PASSWORD=your_password
...
```
- For manual execution:
```console
$ 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 WORDPRESS_SMTP_USER=your_email@gmail.com \
--env WORDPRESS_SMTP_PASSWORD=your_password \
--network wordpress-tier \
--volume /path/to/wordpress-persistence:/bitnami \
bitnami/wordpress-nginx:latest
```
The `WORDPRESS_SMTP_*` environment variables allows you configure the SMTP settings in the application. Please take a look at the environment variables information above for more information.
##### Connect WordPress container to an existing database
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`](https://github.com/bitnami/containers/blob/main/bitnami/wordpress-nginx/docker-compose.yml) file present in this repository:
```diff
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:
```console
$ 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`.
### FIPS configuration in Bitnami Secure Images
@@ -461,46 +270,6 @@ For the WordPress container:
bitnami/wordpress:latest
```
### Upgrade this image
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/containers/tree/main/bitnami/mariadb#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](https://hub.docker.com/r/bitnami/wordpress-nginx/tags/).
#### Step 1: Get the updated image
```console
docker pull bitnami/wordpress-nginx:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker-compose stop wordpress
```
#### Step 3: Take a snapshot of the application state
Follow the steps in [Backing up your container](#backing-up-your-container) to take a snapshot of the current application state.
#### Step 4: Remove the currently running container
Remove the currently running container by executing the following command:
```console
docker-compose rm -v wordpress
```
#### Step 5: Run the new image
Update the image tag in `docker-compose.yml` and re-create your container with the new image:
```console
docker-compose up -d
```
## Customize this image
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.
@@ -522,48 +291,6 @@ FROM bitnami/wordpress-nginx
...
```
Here is an example of extending the image with the following modifications:
- Install the `vim` editor
- Modify the NGINX configuration file
- Modify the ports used by NGINX
```Dockerfile
FROM 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`](https://github.com/bitnami/containers/blob/main/bitnami/wordpress-nginx/docker-compose.yml) file present in this repository to add other features:
```diff
wordpress:
- image: bitnami/wordpress-nginx:latest
+ build: .
ports:
- - 80:8080
- - 443:8443
+ - 80:8181
+ - 443:8143
environment:
+ - PHP_MEMORY_LIMIT=512m
...
```
## Notable Changes
### 6.4.1-debian-11-r5