Drupal with NGINX combines one of the most versatile open source content management systems on the market with the power of the NGINX web server. Drupal is built for high performance and is scalable to many servers, has easy integration via REST, JSON, SOAP and other formats, and features a whopping 15,000 plugins to extend and customize the application for just about any type of website.
https://www.drupal.org/ https://nginx.org/
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-drupal-nginx/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
- All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use
DOCKER_CONTENT_TRUST=1to verify the integrity of the images. - Bitnami container images are released daily with the latest distribution packages available.
This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
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.
NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.
To run this application you need Docker Engine 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.
Running Drupal with a database server is the recommended way. You can either use docker-compose or run the containers manually.
The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-drupal-nginx/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -dIf you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:
- Create a new network for the application and the database:
$ docker network create drupal-tier- Create a volume for MariaDB persistence and create a MariaDB container
$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MARIADB_USER=bn_drupal \
-e MARIADB_DATABASE=bitnami_drupal \
--net drupal-tier \
--volume mariadb_data:/bitnami \
bitnami/mariadb:latest- Create volumes for Drupal persistence and launch the container
$ docker volume create --name drupal_data
$ docker run -d --name drupal -p 80:80 -p 443:443 \
-e ALLOW_EMPTY_PASSWORD=yes \
-e DRUPAL_DATABASE_USER=bn_drupal \
-e DRUPAL_DATABASE_NAME=bitnami_drupal \
--net drupal-tier \
--volume drupal_data:/bitnami
--volume ./drupal-vhosts.conf:/bitnami/nginx/conf/server_blocks/drupal-vhosts.conf \
bitnami/drupal-nginx:latestAccess your application at http://your-ip/
If you remove the container all your data and configurations 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 volume at the /bitnami path. Additionally you should mount a volume for persistence of the MariaDB data.
The above examples define docker volumes namely mariadb_data and drupal_data. The Drupal application state will persist as long as these volumes are not removed.
To avoid inadvertent removal of these 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:
- '/path/to/mariadb-persistence:/bitnami'
...
drupal:
...
volumes:
- '/path/to/drupal-persistence:/bitnami'
...- Create a network (if it does not exist):
$ docker network create drupal-tier- Create a MariaDB container with host volume:
$ docker run -d --name mariadb \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MARIADB_USER=bn_drupal \
-e MARIADB_DATABASE=bitnami_drupal \
--net drupal-tier \
--volume /path/to/mariadb-persistence:/bitnami \
bitnami/mariadb:latestNote: You need to give the container a name in order to Drupal to resolve the host
- Create the Drupal container with host volumes:
$ docker run -d --name drupal -p 80:80 -p 443:443 \
-e ALLOW_EMPTY_PASSWORD=yes \
-e DRUPAL_DATABASE_USER=bn_drupal \
-e DRUPAL_DATABASE_NAME=bitnami_drupal \
--net drupal-tier \
--volume /path/to/drupal-persistence:/bitnami \
bitnami/drupal-nginx:latestBitnami 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/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image
- Get the updated images:
$ docker pull bitnami/drupal-nginx:latest- Stop your container
- For docker-compose:
$ docker-compose stop drupal - For manual execution:
$ docker stop drupal
- Take a snapshot of the application state
$ rsync -a /path/to/drupal-persistence /path/to/drupal-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)Additionally, snapshot the MariaDB data
You can use these snapshots to restore the application state should the upgrade fail.
- Remove the stopped container
- For docker-compose:
$ docker-compose rm drupal - For manual execution:
$ docker rm drupal
- Run the new image
- For docker-compose:
$ docker-compose up drupal - For manual execution (mount the directories if needed):
docker run --name drupal bitnami/drupal-nginx:latest
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:
- For Docker Compose, add the variable name and value under the application section:
drupal:
...
environment:
- DRUPAL_PASSWORD=my_password
...- For manual execution add a
-eoption with each variable and value:
$ docker run -d --name drupal -p 80:80 -p 443:443 \
-e DRUPAL_PASSWORD=my_password \
--net drupal-tier \
--volume /path/to/drupal-persistence:/bitnami \
bitnami/drupal-nginx:latestAvailable variables:
DRUPAL_PROFILE: Drupal installation profile. Default: standardDRUPAL_USERNAME: Drupal application username. Default: userDRUPAL_PASSWORD: Drupal application password. Default: bitnamiDRUPAL_EMAIL: Drupal application email. Default: [email protected]
MARIADB_HOST: Hostname for MariaDB server. Default: mariadbMARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306DRUPAL_DATABASE_NAME: Database name that Drupal will use to connect with the database. Default: bitnami_drupalDRUPAL_DATABASE_USER: Database user that Drupal will use to connect with the database. Default: bn_drupalDRUPAL_DATABASE_PASSWORD: Database password that Drupal will use to connect with the database. No defaults.ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no
MARIADB_HOST: Hostname for MariaDB server. Default: mariadbMARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306MARIADB_ROOT_USER: Database admin user. Default: rootMARIADB_ROOT_PASSWORD: Database password for theMARIADB_ROOT_USERuser. No defaults.MYSQL_CLIENT_CREATE_DATABASE_NAME: New database to be created by the mysql client module. No defaults.MYSQL_CLIENT_CREATE_DATABASE_USER: New database user to be created by the mysql client module. No defaults.MYSQL_CLIENT_CREATE_DATABASE_PASSWORD: Database password for theMYSQL_CLIENT_CREATE_DATABASE_USERuser. No defaults.ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no
The Bitnami Drupal with NGINX 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:
- Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables
APACHE_HTTP_PORT_NUMBERandAPACHE_HTTPS_PORT_NUMBERrespectively. - Adding custom virtual hosts.
- Replacing the 'httpd.conf' file.
- Using custom SSL certificates.
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-nginx
## Put your customizations below
...Here is an example of extending the image with the following modifications:
- Install the
vimeditor - Modify the Apache configuration file
- Modify the ports used by Apache
FROM bitnami/drupal-nginx
LABEL maintainer "Bitnami <[email protected]>"
## Install 'vim'
RUN install_packages vim
## 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 8143Based on the extended image, you can use a Docker Compose file like the one below to add other features:
version: '2'
services:
mariadb:
image: 'bitnami/mariadb:10.3'
environment:
- ALLOW_EMPTY_PASSWORD=yes
- MARIADB_USER=bn_drupal
- MARIADB_DATABASE=bitnami_drupal
volumes:
- 'mariadb_data:/bitnami'
drupal:
build: .
environment:
- MARIADB_HOST=mariadb
- MARIADB_PORT_NUMBER=3306
- DRUPAL_DATABASE_USER=bn_drupal
- DRUPAL_DATABASE_NAME=bitnami_drupal
- ALLOW_EMPTY_PASSWORD=yes
ports:
- '80:8181'
- '443:8143'
volumes:
- 'drupal_data:/bitnami/drupal'
- './drupal-server-block.conf:/opt/bitnami/nginx/conf/server_blocks/drupal-server-block.conf'
depends_on:
- mariadb
volumes:
mariadb_data:
driver: local
drupal_data:
driver: local- This image has been adapted so it's easier to customize. See the Customize this image section for more information.
- 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/certshas 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.
We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
$ docker version) - Output of
$ docker info - Version of this container (
$ echo $BITNAMI_IMAGE_VERSIONinside the container) - The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright 2015-2018 Bitnami
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.