Official Repository

Last pushed: 8 days 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

For more information about this image and its history, please see the relevant manifest file (library/drupal). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the repos/drupal/tag-details.md file in the docker-library/repo-info GitHub repo.

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-compose

Example docker-compose.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: '2'

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

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.

Supported Docker versions

This image is officially supported on Docker version 1.13.1.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Documentation

Documentation for this image is stored in the drupal/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

Docker Pull Command

Comments (16)
aschonbe
a month 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
a month 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
a month 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 ~]#

jmsosso
3 months ago

The better choice to setup this image is to use a Docker Compose file like this to setup your project:

version: '2'

services:
  drupal:
    image: drupal:8.2-apache
    volumes:
      - ./code/modules:/var/www/html/modules
      - ./code/themes:/var/www/html/themes
      - ./data/files:/var/www/html/sites/default/files
      - ./data/private:/var/www/private
    links:
      - mysql

  mysql:
    image: mysql:5.7
    environment:
      MYSQL_ROOT_PASSWORD: root
      MYSQL_USER: drupal
      MYSQL_PASSWORD: 123456
      MYSQL_DATABASE: database_name
    volumes:
      - ./data/mysql:/var/lib/mysql

Don't forget to change permissions before start the installation process:
sudo chmod a+w data/private/ data/files/

But if you want a more advanced setup you can see this guide (sorry in spanish):

https://www.servinube.net/blog/como-crear-un-nuevo-proyecto-de-drupal-8-con-composer

aschonbe
4 months ago

Drupal 8.2.2 has been released as of Nov. 2, 2016. The GitHub repository has been updated to reflect this (https://github.com/docker-library/drupal/commit/9cd16801643ce9a8373bd74c74ff1a1565842795) the same day.

I don't see a 8.2.2 tag here, nor does "latest" tag seem to be updated with this update. Am I missing something - like a review process that I'm not seeing? What needs to happen to make this update available? Is there a way for me to help contribute in expediting this process?

npcoder
6 months ago

Is there any documentation regarding Drupal 8 and MS SQL?

csandanov
7 months ago

If you want to have more advanced setup for Drupal (with redis, solr, varnish, pma, mailhog) check out this open-source initiative http://docker4drupal.org

codestrider35
a year ago

Linked drupal to mysql with a password set, however everytime I try to setup the database when in drupal, I get an error: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known

kbemelmans
a year ago

ahuffman: There is a discussion going on about it at https://github.com/docker-library/drupal/issues/3

ahuffman
a year ago

Why is there not a VOLUMES at /var/www/html? There's no way to persist installed modules or static content without that. If I bind mount at /var/www/html the site will not start, because the content at /var/www/html does not get copied to the bind mounted /var/www/html without a VOLUME entry. The developers of this container should take a look at what joomla and wordpress are doing.