Official Repository

Last pushed: a day ago
Short Description
Drupal is an open source content management platform powering millions of websites and applications.
Full Description

Supported tags and respective Dockerfile links

Quick reference

What is Drupal?

Drupal is a free and open-source content-management framework written in PHP and distributed under the GNU General Public License. It is used as a back-end framework for at least 2.1% of all Web sites worldwide ranging from personal blogs to corporate, political, and government sites including WhiteHouse.gov and data.gov.uk. It is also used for knowledge management and business collaboration.

wikipedia.org/wiki/Drupal

How to use this image

The basic pattern for starting a drupal instance is:

$ docker run --name some-drupal -d drupal

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-drupal -p 8080:80 -d drupal

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

There are multiple database types supported by this image, most easily used via standard container linking. In the default configuration, SQLite can be used to avoid a second container and write to flat-files. More detailed instructions for different (more production-ready) database types follow.

When first accessing the webserver provided by this image, it will go through a brief setup process. The details provided below are specifically for the "Set up database" step of that configuration process.

MySQL

$ docker run --name some-drupal --link some-mysql:mysql -d drupal
  • Database type: MySQL, MariaDB, or equivalent
  • Database name/username/password: <details for accessing your MySQL instance> (MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE; see environment variables in the description for mysql)
  • ADVANCED OPTIONS; Database host: mysql (for using the /etc/hosts entry added by --link to access the linked container's MySQL instance)

PostgreSQL

$ docker run --name some-drupal --link some-postgres:postgres -d drupal
  • Database type: PostgreSQL
  • Database name/username/password: <details for accessing your PostgreSQL instance> (POSTGRES_USER, POSTGRES_PASSWORD; see environment variables in the description for postgres)
  • ADVANCED OPTIONS; Database host: postgres (for using the /etc/hosts entry added by --link to access the linked container's PostgreSQL instance)

Volumes

By default, this image does not include any volumes. There is a lot of good discussion on this topic in docker-library/drupal#3, which is definitely recommended reading.

There is consensus that /var/www/html/modules, /var/www/html/profiles, and /var/www/html/themes are things that generally ought to be volumes (and might have an explicit VOLUME declaration in a future update to this image), but handling of /var/www/html/sites is somewhat more complex, since the contents of that directory do need to be initialized with the contents from the image.

If using bind-mounts, one way to accomplish pre-seeding your local sites directory would be something like the following:

$ docker run --rm drupal tar -cC /var/www/html/sites . | tar -xC /path/on/host/sites

This can then be bind-mounted into a new container:

$ docker run --name some-drupal --link some-postgres:postgres -d \
    -v /path/on/host/modules:/var/www/html/modules \
    -v /path/on/host/profiles:/var/www/html/profiles \
    -v /path/on/host/sites:/var/www/html/sites \
    -v /path/on/host/themes:/var/www/html/themes \
    drupal

Another solution using Docker Volumes:

$ docker volume create drupal-sites
$ docker run --rm -v drupal-sites:/temporary/sites drupal cp -aRT /var/www/html/sites /temporary/sites
$ docker run --name some-drupal --link some-postgres:postgres -d \
    -v drupal-modules:/var/www/html/modules \
    -v drupal-profiles:/var/www/html/profiles \
    -v drupal-sites:/var/www/html/sites \
    -v drupal-themes:/var/www/html/themes \

... via docker stack deploy or docker-compose

Example stack.yml for drupal:

# Drupal with PostgreSQL
#
# Access via "http://localhost:8080"
#   (or "http://$(docker-machine ip):8080" if using docker-machine)
#
# During initial Drupal setup,
# Database type: PostgreSQL
# Database name: postgres
# Database username: postgres
# Database password: example
# ADVANCED OPTIONS; Database host: postgres

version: '3.1'

services:

  drupal:
    image: drupal:8.2-apache
    ports:
      - 8080:80
    volumes:
      - /var/www/html/modules
      - /var/www/html/profiles
      - /var/www/html/themes
      # this takes advantage of the feature in Docker that a new anonymous
      # volume (which is what we're creating here) will be initialized with the
      # existing content of the image at the same location
      - /var/www/html/sites
    restart: always

  postgres:
    image: postgres:9.6
    environment:
      POSTGRES_PASSWORD: example
    restart: always

Run docker stack deploy -c stack.yml drupal (or docker-compose -f stack.yml up), wait for it to initialize completely, and visit http://swarm-ip:8080, http://localhost:8080, or http://host-ip:8080 (as appropriate). When installing select postgres as database with the following parameters: dbname=postgres user=postgres pass=example hostname=postgres

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.
  • Repository Links can ensure that your image is also rebuilt any time drupal is updated.

License

View license information for the software contained in this image.

Docker Pull Command

Comments (23)
sebastianstaeubert
5 days ago

An Image for drupal 8.3.7 would be nice.

csandanov
2 months ago

For a complete Drupal stack check out https://github.com/wodby/docker4drupal

ronnf89
2 months ago

@swardet I have bind-mounts local project for development purpose, I have running my drupal container but I don't know how to use drupal console in container, please help me.

miclan
3 months ago

@swardet
When you are filling db info, there is a "more" below, you should fill db hostname.

swardet
3 months ago

i pull mysql, then pull drupal (8.3.2) using following:

docker run --name t-mysql -e MYSQL_ROOT_PASSWORD=password -d mysql:latest

docker run --name t-drupal --link t-mysql:mysql -p 8090:80 -d drupal

both elegantly install, start, etc.

i go to http://192.168.99.100:8090/core/install.php and everything loads up like it should.

i get to fourth drupal setup option Set up database and this is where it abends. perhaps it's user error, but i don't think so - i've worked with php/mysql for 13yrs - pretty straight forward.

the abend is "Failed to connect to your database server. The server reports the following message: SQLSTATE[HY000] [2002] No such file or directory."

no matter what options i enter it doesn't get past this point. i suspect "Database name" is the culprit and the name MUST be specified in the docker run command, but it's not doc'd.

I'm selecting "database type" MySQL
Database name is _drupal
Database username is root
Database password is password

ideas?

hvaara
4 months ago

kvdocker1: Pull request was just merged, so soon :) docker-library/official-images#2882

kvdocker1
4 months ago

Is there a planned release date for the 8.2.8 and 8.3.1 images? Thanks.

aschonbe
7 months ago

Pending pull request to update to versions 8.2.6 and 7.54 of Drupal: docker-library/official-images#2612 - Feb. 2, 2017

aschonbe
7 months ago

@alexus : Try checking if port 8080 is already taken or use another (say 8081). The rest of that error usually states: "Error starting userland proxy: listen tcp 0.0.0.0:8080: bind: address already in use." and is more self-explanatory.

alexus
7 months ago

I'm getting this weird error:

[root@7dvdsc01 ~]# docker run -p 8080:80 -d drupal
cb0a0e6b9b3c582e28e4c0c44bc8360e81d08b480a451a0821649c4363ade528
/usr/bin/docker-latest: Error response from daemon: driver failed programming external connectivity on endpoint reverent_newton (88f66e815eb12c5949965e9434c94855205b5705f07b8ffaa54b065f91a86712): Error starting userland proxy:.
[root@7dvdsc01 ~]#