public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-17 16:21:43 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/drupal] Release 11.3.3-debian-12-r5 (#91195)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-02 18:45:21 +01:00
committed by GitHub
parent 7006bf33cc
commit 7fef71b906
2 changed files with 31 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/drupal/11/debian-12/Dockerfile
+6 -6
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-25T08:44:27Z" \
org.opencontainers.image.created="2026-03-02T17:16:38Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/drupal/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/drupal" \
@@ -29,12 +29,12 @@ 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-162-linux-${OS_ARCH}-debian-12" \
"php-8.4.18-4-linux-${OS_ARCH}-debian-12" \
"php-8.4.18-7-linux-${OS_ARCH}-debian-12" \
"mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \
"libphp-8.4.18-3-linux-${OS_ARCH}-debian-12" \
"libphp-8.4.18-5-linux-${OS_ARCH}-debian-12" \
"postgresql-lib-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"apache-2.4.66-0-linux-${OS_ARCH}-debian-12" \
"drupal-11.3.3-0-linux-${OS_ARCH}-debian-12" \
"apache-2.4.66-1-linux-${OS_ARCH}-debian-12" \
"drupal-11.3.3-1-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -61,7 +61,7 @@ ENV APACHE_HTTPS_PORT_NUMBER="" \
APACHE_HTTP_PORT_NUMBER="" \
APP_VERSION="11.3.3" \
BITNAMI_APP_NAME="drupal" \
IMAGE_REVISION="4" \
IMAGE_REVISION="5" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/mysql/bin:/opt/bitnami/postgresql-lib/bin:/opt/bitnami/apache/bin:/opt/bitnami/drupal/vendor/bin:$PATH"
bitnami/drupal/README.md
+25 -23
View File
@@ -1,13 +1,11 @@
# Bitnami Secure Image for Drupal
## What is Drupal?
> Drupal is one of the most versatile open source content management systems in the world. It is pre-configured with the Ctools and Views modules, Drush and Let's Encrypt auto-configuration support.
[Overview of Drupal](https://drupal.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.
## TL;DR
## <a id="tl-dr"></a> TL;DR
```console
docker run --name drupal bitnami/drupal:latest
@@ -16,7 +14,7 @@ docker run --name drupal bitnami/drupal: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 d
eployment.
## Why use Bitnami Secure Images?
## <a id="why-use-bitnami-secure-images"></a> 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?
@@ -33,19 +31,19 @@ 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).
## Why use a non-root container?
## <a id="why-non-root"></a> 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).
## How to deploy Drupal in Kubernetes?
## <a id="how-to-deploy-in-kubernetes"></a> How to deploy Drupal 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 Drupal Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/drupal).
## Supported tags and respective `Dockerfile` links
## <a id="supported-tags"></a> 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).
## Get this image
## <a id="get-this-image"></a> Get this image
The recommended way to get the Bitnami Drupal Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/drupal).
@@ -67,11 +65,11 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## How to use this image
## <a id="how-to-use-this-image"></a> How to use this image
Drupal 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.
## Persisting your application
## <a id="persisting-your-application"></a> 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.
@@ -79,11 +77,15 @@ For persistence you should mount a directory at the `/bitnami/drupal` path. If t
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: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## Configuration
## <a id="configuration"></a> Configuration
### Environment variables
The following section describes the supported environment variables
### <a id="environment-variables"></a> Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
@@ -129,13 +131,13 @@ When you start the Drupal image, you can adjust the configuration of the instanc
The `DRUPAL_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.
### FIPS configuration in Bitnami Secure Images
### <a id="fips-configuration"></a> FIPS configuration in Bitnami Secure Images
The Bitnami Drupal 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`.
## Logging
## <a id="logging"></a> Logging
The Bitnami Drupal Docker image sends the container logs to `stdout`. To view the logs:
@@ -151,9 +153,9 @@ docker-compose logs drupal
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
## <a id="maintenance"></a> Maintenance
### Backing up your container
### <a id="backing-up-your-container"></a> Backing up your container
To backup your data, configuration and logs, follow these simple steps:
@@ -178,7 +180,7 @@ docker run --rm -v /path/to/drupal-backups:/backups --volumes-from drupal busybo
cp -a /bitnami/drupal /backups/latest
```
### Restoring a backup
### <a id="restoring-a-backup"></a> Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
@@ -202,11 +204,11 @@ For the Drupal container:
bitnami/drupal:latest
```
## Customize this image
## <a id="customize-this-image"></a> Customize this image
The Bitnami Drupal Docker image is designed to be extended so it can be used as the base image for your custom web applications.
### Extend this image
### <a id="extend-this-image"></a> Extend this image
Before extending this image, please note there are certain configuration settings you can modify using the original image:
@@ -219,11 +221,11 @@ If your desired customizations cannot be covered using the methods mentioned abo
```Dockerfile
FROM bitnami/drupal
## Put your customizations below
## <a id="put-your-customizations-below"></a> Put your customizations below
...
```
## Notable Changes
## <a id="notable-changes"></a> Notable Changes
## 8.9.2-debian-10-r3 and 9.0.2-debian-10-r3
@@ -244,7 +246,7 @@ FROM bitnami/drupal
- The drupal container now uses drush to install and update the Drupal application.
## License
## <a id="license"></a> License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.