bitnami/drupal
Bitnami container image for Drupal
5M+
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 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.
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 section for a more secure d eployment.
Looking to use Drupal in production? Try VMware Tanzu Application Catalog, the commercial edition of the Bitnami catalog.
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.
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.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Starting December 10th 2024, only the latest stable branch of any container will receive updates in the free Bitnami catalog. To access up-to-date releases for all upstream-supported branches, consider upgrading to Bitnami Premium. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
Please check the Bitnami Premium page in our partner Arrow Electronics for more information.
Dockerfile
linksLearn 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 bitnami/containers GitHub repo.
The recommended way to get the Bitnami Drupal Docker Image is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/drupal:latest
To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
docker pull bitnami/drupal:[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.
git clone https://github.com/bitnami/containers.git
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
Drupal requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.
Step 1: Create a network
docker network create drupal-network
Step 2: Create a volume for MariaDB persistence and create a MariaDB container
$ docker volume create --name mariadb_data
docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_drupal \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_drupal \
--network drupal-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
Step 3: Create volumes for Drupal persistence and launch the container
$ docker volume create --name drupal_data
docker run -d --name drupal \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env DRUPAL_DATABASE_USER=bn_drupal \
--env DRUPAL_DATABASE_PASSWORD=bitnami \
--env DRUPAL_DATABASE_NAME=bitnami_drupal \
--network drupal-network \
--volume drupal_data:/bitnami/drupal \
bitnami/drupal:latest
Access your application at http://your-ip:8080/
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/drupal/docker-compose.yml > docker-compose.yml
docker-compose up -d
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.
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.
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/drupal
path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the MariaDB data.
The above examples define the Docker volumes named mariadb_data and drupal_data. The Drupal application state will persist as long as volumes are not removed.
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.
This requires a minor change to the docker-compose.yml
file present in this repository:
mariadb:
...
volumes:
- - 'mariadb_data:/bitnami/mariadb'
+ - /path/to/mariadb-persistence:/bitnami/mariadb
...
drupal:
...
volumes:
- - 'drupal_data:/bitnami/drupal'
+ - /path/to/drupal-persistence:/bitnami/drupal
...
-volumes:
- mariadb_data:
- driver: local
- drupal_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
.
Step 1: Create a network (if it does not exist)
docker network create drupal-network
Step 2. Create a MariaDB container with host volume
docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_drupal \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_drupal \
--network drupal-network \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
Step 3. Create the Drupal container with host volumes
docker run -d --name drupal \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env DRUPAL_DATABASE_USER=bn_drupal \
--env DRUPAL_DATABASE_PASSWORD=bitnami \
--env DRUPAL_DATABASE_NAME=bitnami_drupal \
--network drupal-network \
--volume /path/to/drupal-persistence:/bitnami/drupal \
bitnami/drupal:latest
Customizable environment variables
Name | Description | Default Value |
---|---|---|
DRUPAL_DATA_TO_PERSIST | Files to persist relative to the Drupal installation directory. To provide multiple values, separate them with a whitespace. | sites/ themes/ modules/ profiles/ |
DRUPAL_PROFILE | Drupal installation profile. | standard |
DRUPAL_SITE_NAME | Drupal blog name. | My blog |
DRUPAL_SKIP_BOOTSTRAP | Whether to perform initial bootstrapping for the application. | nil |
DRUPAL_ENABLE_MODULES | Comma or space separated list of installed modules to enable during the first initialization. | nil |
DRUPAL_CONFIG_SYNC_DIR | Drupal sync configuration directory location. Only used when DRUPAL_SKIP_BOOTSTRAP is enabled. | nil |
DRUPAL_HASH_SALT | Drupal string used to generate random values. Only used when DRUPAL_SKIP_BOOTSTRAP is enabled. | nil |
DRUPAL_USERNAME | Drupal user name. | user |
DRUPAL_PASSWORD | Drupal user password. | bitnami |
DRUPAL_EMAIL | Drupal user e-mail address. | user@example.com |
DRUPAL_SMTP_HOST | Drupal SMTP server host. | nil |
DRUPAL_SMTP_PORT_NUMBER | Drupal SMTP server port number. | 25 |
DRUPAL_SMTP_USER | Drupal SMTP server user. | nil |
DRUPAL_SMTP_PASSWORD | Drupal SMTP server user password. | nil |
DRUPAL_SMTP_PROTOCOL | Drupal SMTP server protocol. | standard |
DRUPAL_DATABASE_HOST | Database server host. | $DRUPAL_DEFAULT_DATABASE_HOST |
DRUPAL_DATABASE_PORT_NUMBER | Database server port. | 3306 |
DRUPAL_DATABASE_NAME | Database name. | bitnami_drupal |
DRUPAL_DATABASE_USER | Database user name. | bn_drupal |
DRUPAL_DATABASE_PASSWORD | Database user password. | nil |
DRUPAL_DATABASE_TLS_CA_FILE | TLS CA certificate for connections. | nil |
Read-only environment variables
Name | Description | Value |
---|---|---|
DRUPAL_BASE_DIR | Drupal installation directory. | ${BITNAMI_ROOT_DIR}/drupal |
DRUPAL_CONF_FILE | Configuration file for Drupal. | ${DRUPAL_BASE_DIR}/sites/default/settings.php |
DRUPAL_MODULES_DIR | Drupal modules directory. | ${DRUPAL_BASE_DIR}/modules |
DRUPAL_VOLUME_DIR | Drupal directory for mounted configuration files. | ${BITNAMI_VOLUME_DIR}/drupal |
DRUPAL_MOUNTED_CONF_FILE | Mounted configuration file for Drupal. It will be copied to the Drupal installation directory during the initialization process. | ${DRUPAL_VOLUME_DIR}/settings.php |
DRUPAL_DEFAULT_DATABASE_HOST | Default database server host. | mariadb |
PHP_DEFAULT_MEMORY_LIMIT | Default PHP memory limit. | 256M |
When you start the Drupal 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:
docker-compose.yml
file present in this repository:drupal:
...
environment:
- DRUPAL_PASSWORD=my_password
...
For manual execution add a --env
option with each variable and value:
docker run -d --name drupal -p 80:8080 -p 443:8443 \
--env DRUPAL_PASSWORD=my_password \
--network drupal-tier \
--volume /path/to/drupal-persistence:/bitnami \
bitnami/drupal:latest
Example
This would be an example of SMTP configuration using a Gmail account:
docker-compose.yml
file present in this repository: drupal:
...
environment:
- DRUPAL_DATABASE_USER=bn_drupal
- DRUPAL_DATABASE_NAME=bitnami_drupal
- ALLOW_EMPTY_PASSWORD=yes
- DRUPAL_SMTP_HOST=smtp.gmail.com
- DRUPAL_SMTP_PORT=587
- DRUPAL_SMTP_USER=your_email@gmail.com
- DRUPAL_SMTP_PASSWORD=your_password
- DRUPAL_SMTP_PROTOCOL=tls
...
For manual execution:
docker run -d --name drupal -p 80:8080 -p 443:8443 \
--env DRUPAL_DATABASE_USER=bn_drupal \
--env DRUPAL_DATABASE_NAME=bitnami_drupal \
--env DRUPAL_SMTP_HOST=smtp.gmail.com \
--env DRUPAL_SMTP_PORT=587 \
--env DRUPAL_SMTP_USER=your_email@gmail.com \
--env DRUPAL_SMTP_PASSWORD=your_password \
--env DRUPAL_SMTP_PROTOCOL=tls \
--network drupal-tier \
--volume /path/to/drupal-persistence:/bitnami \
bitnami/drupal:latest
The Bitnami Drupal Docker image sends the container logs to stdout
. To view the logs:
docker logs drupal
Or using Docker Compose:
docker-compose logs drupal
You can configure the containers logging driver using the --log-driver
option if you wish to consume the container logs differently. In the default configuration docker uses the json-file
driver.
To backup your data, configuration and logs, follow these simple steps:
Step 1: Stop the currently running container
docker stop drupal
Or using Docker Compose:
docker-compose stop drupal
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.
docker run --rm -v /path/to/drupal-backups:/backups --volumes-from drupal busybox \
cp -a /bitnami/drupal /backups/latest
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
$ 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 Drupal container:
$ docker run -d --name drupal \
...
- --volume /path/to/drupal-persistence:/bitnami/drupal \
+ --volume /path/to/drupal-backups/latest:/bitnami/drupal \
bitnami/drupal:latest
Bitnami provides up-to-date versions of MariaDB and Drupal, 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 Drupal container. For the MariaDB upgrade see: https://github.com/bitnami/containers/tree/main/bitnami/mariadb#upgrade-this-image
Step 1: Get the updated image
docker pull bitnami/drupal:latest
Step 2: Stop the running container
Stop the currently running container using the command
docker-compose stop drupal
Step 3: Take a snapshot of the application state
Follow the steps in 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:
docker-compose rm -v drupal
Step 5: Run the new image
Update the image tag in docker-compose.yml
and re-create your container with the new image:
docker-compose up -d
The Bitnami Drupal Docker image is designed to be extended so it can be used as the base image for your custom web applications.
Before extending this image, please note there are certain configuration settings you can modify using the original image:
APACHE_HTTP_PORT_NUMBER
and APACHE_HTTPS_PORT_NUMBER
respectively.If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:
FROM bitnami/drupal
## Put your customizations below
...
Here is an example of extending the image with the following modifications:
vim
editorFROM bitnami/drupal
## Change user to perform privileged actions
USER 0
## Install 'vim'
RUN install_packages vim
## Revert to the original non-root user
USER 1001
## Enable mod_ratelimit module
RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf
## Modify the ports used by Apache by default
# It is also possible to change these environment variables at runtime
ENV APACHE_HTTP_PORT_NUMBER=8181
ENV APACHE_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143
Based on the extended image, you can update the docker-compose.yml
file present in this repository to add other features:
drupal:
- image: bitnami/drupal:latest
+ build: .
ports:
- - '80:8080'
- - '443:8443'
+ - '80:8181'
+ - '443:8143'
environment:
+ - PHP_MEMORY_LIMIT=512m
...
root
user and the Apache daemon was started as the daemon
user. From now on, both the container and the Apache daemon run as user 1001
. You can revert this behavior by changing USER 1001
to USER root
in the Dockerfile, or user: root
in docker-compose.yml
. Consequences:
8080/8443
instead of 80/443
.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 https://github.com/bitnami/containers/blob/main/bitnami/drupal/README.md