Estimated reading time: 4 minutes

The comprehensive CMS for small to medium sized businesses and non-profits.

GitHub repo:

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Hub page for this image at

Supported tags and respective Dockerfile links

Quick reference

What is Backdrop CMS?

Backdrop CMS is a comprehensive Content Management System for small to medium sized businesses and non-profits. It is a fork of the Drupal project.

Backdrop CMS enables people to build highly customized websites, affordably, through collaboration and open source software. For more on the Backdrop’s philosophy see


How to use this image

The basic pattern for starting a backdrop instance is:

$ docker run --name some-backdrop --link some-mysql:mysql -d backdrop

The following environment variables are also honored for configuring your Backdrop CMS instance:

  • -e BACKDROP_DB_HOST=... (defaults to the IP and port of the linked mysql container)
  • -e BACKDROP_DB_USER=... (defaults to “root”)
  • -e BACKDROP_DB_PASSWORD=... (defaults to the value of the MYSQL_ROOT_PASSWORD environment variable from the linked mysql container)
  • -e BACKDROP_DB_NAME=... (defaults to “backdrop”)
  • -e BACKDROP_DB_PORT=... (defaults to 3306)
  • -e BACKDROP_DB_DRIVER=... (defaults to “mysql”)

The BACKDROP_DB_NAME must already exist on the given MySQL server. Check out the official mysql image for more info on spinning up a DB.

If you’d like to be able to access the instance from the host without the container’s IP, standard port mappings can be used:

$ docker run --name some-backdrop --link some-mysql:mysql -p 8080:80 -d backdrop

Then, access it via http://localhost:8080 or http://host-ip:8080 in a browser.

If you’d like to use an external database instead of a linked mysql container, specify the hostname and port with BACKDROP_DB_HOST/BACKDROP_DB_PORT along with the password in BACKDROP_DB_PASSWORD and the username in BACKDROP_DB_USER (if it is something other than root):

$ docker run --name some-backdrop \
  -e BACKDROP_DB_PORT=10432 \
  -d backdrop

... via docker-compose

Example docker-compose.yml for backdrop:

  image: backdrop
    - db:mysql
    - 8080:80

  image: mysql
    MYSQL_USER: backdrop
    MYSQL_PASSWORD: backdrop
    MYSQL_DATABASE: backdrop

Run docker-compose up, wait for it to initialize completely, and visit http://localhost:8080 or http://host-ip:8080.

Adding additional libraries / extensions

This image does not provide any additional PHP extensions or other libraries, even if they are required by popular plugins. There are an infinite number of possible plugins, and they potentially require any extension PHP supports. Including every PHP extension that exists would dramatically increase the image size.

If you need additional PHP extensions, you’ll need to create your own image FROM this one. The documentation of the php image explains how to compile additional extensions. Additionally, the drupal:7 Dockerfile has an example of doing this.

The following Docker Hub features can help with the task of keeping your dependent images up-to-date:

  • Automated Builds let Docker Hub automatically build your Dockerfile each time you push changes to it.


View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository’s backdrop/ directory.

As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

library, sample, backdrop