• 8.8-2.x, latest (Dockerfile)
• dev (Dockerfile)

This image is updated via pull requests to the INsReady/docker-drupal-commerce GitHub repo.

Drupal Commerce is used to build eCommerce websites and applications of all sizes. At its core it is lean and mean, enforcing strict development standards and leveraging the greatest features of Drupal and major modules like Views and Rules for maximum flexibility.

Drupal Commerce Documentation

The basic pattern for starting a drupal commerce instance is:

$ docker run --name some-drupal -d insready/drupal-commerce

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 insready/drupal-commerce

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.

$ docker run --name some-drupal --link some-mysql:mysql -d insready/drupal-commerce

• 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)

$ docker run --name some-drupal --link some-postgres:postgres -d insready/drupal-commerce

• 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)

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.

View license information for the software contained in this image.

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

If you have any problems with or questions about this image, please contact us through a GitHub issue.

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

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.