Awesome

Dolibarr on Docker

Docker image for Dolibarr ERP & CRM Open source web suite.

Dolibarr is a modern software package to manage your organization's activity (contacts, quotes, invoices, orders, stocks, agenda, hr, expense reports, accountancy, ecm, manufacturing, ...).

More information

Available versions/tags on Docker

• 15.0.3-php7.4 15.0.3 15
• 16.0.5-php8.1 16.0.5 16
• 17.0.4-php8.1 17.0.4 17
• 18.0.6-php8.1 18.0.6 18
• 19.0.4-php8.2 19.0.4 19
• 20.0.2-php8.2 20.0.2 20 latest
• develop

Dolibarr versions 14 and lower are no more updated on docker hub. You can get them as standard zip package from Dolibarr official web site

Supported architectures

Linux x86-64 (amd64), ARMv7 32-bit (arm32v7 :warning: MariaDB/Mysql docker images don't support it) and ARMv8 64-bit (arm64v8)

How to run this image ?

This image is based on the official PHP repository and the official Dolibarr repository. It is build using the tools saved in the Dolibarr docker build repository.

This image does not contains database, so you need to link it with a database container. Let's use Docker Compose to integrate it with MariaDB (you can also use MySQL if you prefer):

If you want to have a persistent database and dolibarr data files after reboot or upgrade, you must first create a directory /home/dolibarr_mariadb, /home/dolibarr_documents and /home/dolibarr_custom on your host to store persistent files, respectively, of the database, of the Dolibarr document files and of the installed external Dolibarr modules.

mkdir /home/dolibarr_mariadb /home/dolibarr_documents /home/dolibarr_custom;

Then, create a docker-compose.yml file as following:

# Edit this file then run 
# docker-compose up -d
# docker-compose logs

services:
    mariadb:
        image: mariadb:latest
        environment:
            MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD:-root}
            MYSQL_DATABASE: ${MYSQL_DATABASE:-dolidb}
            MYSQL_USER: ${MYSQL_USER:-dolidbuser}
            MYSQL_PASSWORD: ${MYSQL_PASSWORD:-dolidbpass}

        volumes:
            - /home/dolibarr_mariadb:/var/lib/mysql

    web:
    	# Choose the version of image to install
    	# dolibarr/dolibarr:latest (the latest stable version)
    	# dolibarr/dolibarr:develop
    	# dolibarr/dolibarr:x.y.z
        image: dolibarr/dolibarr:latest
        environment:
            WWW_USER_ID: ${WWW_USER_ID:-1000}
            WWW_GROUP_ID: ${WWW_GROUP_ID:-1000}
            DOLI_DB_HOST: ${DOLI_DB_HOST:-mariadb}
            DOLI_DB_NAME: ${DOLI_DB_NAME:-dolidb}
            DOLI_DB_USER: ${DOLI_DB_USER:-dolidbuser}
            DOLI_DB_PASSWORD: ${DOLI_DB_PASSWORD:-dolidbpass}
            DOLI_URL_ROOT: "${DOLI_URL_ROOT:-http://0.0.0.0}"
            DOLI_ADMIN_LOGIN: "${DOLI_ADMIN_LOGIN:-admin}"
            DOLI_ADMIN_PASSWORD: "${DOLI_ADMIN_PASSWORD:-admin}"
            DOLI_CRON: ${DOLI_CRON:-0}
            DOLI_INIT_DEMO: ${DOLI_INIT_DEMO:-0}
            DOLI_COMPANY_NAME: ${DOLI_COMPANY_NAME:-MyBigCompany}

        ports:
            - "80:80"
        links:
            - mariadb
        volumes:
            - /home/dolibarr_documents:/var/www/documents
            - /home/dolibarr_custom:/var/www/html/custom

Then build and run all services (-d is to run in background)

sudo docker-compose up -d

You can check the web and the mariadb containers are up and see logs with

sudo docker-compose ps

sudo docker-compose logs

Once the log shows that the start is complete, go to http://0.0.0.0 to access to the new Dolibarr installation, first admin login is admin/admin.

Note: If the host port 80 is already used, you can replace "80:80" with "xx:80" where xx a free port on the host. You will be able to access the Dolibarr using the URL http://0.0.0.0:xx

Other examples:

You can find several examples in the examples directory, such as:

• Running Dolibarr with a letsencrypt certificate
• Running Dolibarr with a mysql server
• Running Dolibarr with a Traefik reverse proxy
• Running Dolibarr with secrets

Upgrading Dolibarr version and migrating DB

Warning: Only data stored into persistent directories will not be lost after an upgrade of containers.

Remove the install.lock file. The install.lock file is located inside the container volume /var/www/documents.

sudo docker exec nameofwebcontainer bash -c "rm -f /var/www/documents/install.lock"

or

sudo docker exec -it nameofwebcontainer bash

rm -f /var/www/documents/install.lock; exit

Then start an updated version container.

sudo docker-compose pull

sudo docker-compose up -d

sudo docker-compose logs

Ensure that env DOLI_INSTALL_AUTO is set to 1 so it will migrate Database to the new version. You can still use the standard way to upgrade through web interface.

Environment variables summary

You can use the following variables for a better customization of your docker-compose file.

Some environment variables are compatible with docker secrets behaviour, just add the _FILE suffix to var name and point the value file to read. Environment variables that are compatible with docker secrets:

• DOLI_DB_USER => DOLI_DB_USER_FILE
• DOLI_DB_PASSWORD => DOLI_DB_PASSWORD_FILE
• DOLI_ADMIN_LOGIN => DOLI_ADMIN_LOGIN_FILE
• DOLI_ADMIN_PASSWORD => DOLI_ADMIN_PASSWORD_FILE
• DOLI_CRON_KEY => DOLI_CRON_KEY_FILE
• DOLI_CRON_USER => DOLI_CRON_USER_FILE
• DOLI_INSTANCE_UNIQUE_ID => DOLI_INSTANCE_UNIQUE_ID_FILE

Add post-deployment and before starting scripts

It is possible to execute *.sh, *.sql and/or *.php custom files at the end of a deployment or before starting Apache by mounting volumes. For scripts to execute during deployment, mount volume in /var/www/scripts/docker-init.d. For scripts to execute before Apache start, mount volume in /var/www/scripts/before-starting.d.

\docker-init.d
|- custom_script.sql
|- custom_script.php
|- custom_script.sh

Mount the volumes with compose file :

services:
    mariadb:
        image: mariadb:latest
        environment:
            MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD:-root}
            MYSQL_DATABASE: ${MYSQL_DATABASE:-dolidb}
            MYSQL_USER: ${MYSQL_USER:-dolidbuser}
            MYSQL_PASSWORD: ${MYSQL_PASSWORD:-dolidbpass}

    web:
    	# Choose the version of image to install
    	# dolibarr/dolibarr:latest (the latest stable version)
    	# dolibarr/dolibarr:develop
    	# dolibarr/dolibarr:x.y.z
        image: dolibarr/dolibarr
        environment:
            DOLI_DB_HOST: ${DOLI_DB_HOST:-mariadb}
            DOLI_DB_NAME: ${DOLI_DB_NAME:-dolidb}
            DOLI_DB_USER: ${DOLI_DB_USER:-dolidbuser}
            DOLI_DB_PASSWORD: ${DOLI_DB_PASSWORD:-dolidbpass}
            DOLI_URL_ROOT: "${DOLI_URL_ROOT:-http://0.0.0.0}"
            DOLI_ADMIN_LOGIN: "${DOLI_ADMIN_LOGIN:-admin}"
            DOLI_ADMIN_PASSWORD: "${DOLI_ADMIN_PASSWORD:-admin}"
            DOLI_INIT_DEMO: ${DOLI_INIT_DEMO:-0}
            WWW_USER_ID: ${WWW_USER_ID:-1000}
            WWW_GROUP_ID: ${WWW_GROUP_ID:-1000}
        volumes :
          - volume-scripts:/var/www/scripts/docker-init.d
          - before-starting-scripts:/var/www/scripts/before-starting.d
        ports:
            - "80:80"
        links:
            - mariadb

Early support for PostgreSQL

Setting DOLI_DB_TYPE to pgsql enable Dolibarr to run with a PostgreSQL database. When set to use pgsql, Dolibarr must be installed manually on it's first execution:

• Browse to http://0.0.0.0/install;
• Follow the installation setup;
• Add install.lock inside the container volume /var/www/html/documents (ex docker-compose exec services-data_dolibarr_1 /bin/bash -c "touch /var/www/html/documents/install.lock").

When setup this way, to upgrade version the use of the web interface is mandatory:

• Remove the install.lock file (ex docker-compose exec services-data_dolibarr_1 /bin/bash -c "rm -f /var/www/html/documents/install.lock").

• Browse to http://0.0.0.0/install;

• Upgrade DB;

• Add install.lock inside the container volume /var/www/html/documents (ex docker-compose exec services-data_dolibarr_1 /bin/bash -c "touch /var/www/html/documents/install.lock").

Trouble shooting

If you get error "urllib3.exceptions.URLSchemeUnknown: Not supported URL scheme http+docker" during docker-compose, try to upgrade or downgrade the pip package: pip install requests==2.31.0