I’m setting up Dolibarr with Docker to manage a small web project and would like to make sure I’m following current best practices before going live.
For those who’ve deployed Dolibarr this way, did you run into any issues with file permissions, database initialization, or upgrades? I’d also appreciate any recommendations for backup strategies or configuration tips that have worked well in production.
If there are any official guides or community resources you’d recommend so I can learn more about maintaining a Docker-based installation, I’d be grateful for the suggestions.
Thanks in advance for your help!
The main gotchas with Docker + Dolibarr: map persistent volumes for both /var/www/documents (file uploads and generated documents) and your database data directory — lose either and you lose data. The official image is dolibarr/dolibarr on Docker Hub; pair it with a MariaDB container via docker-compose. File permissions are usually fine if your volumes are writable by www-data (UID 33 on Debian-based images).
For upgrades, the image supports a DOLI_VERSION env var that triggers the upgrade wizard automatically on container restart — read the image docs carefully before doing this in production, and always back up first. For backups, mysqldump the database and snapshot the documents volume; you need both together to restore cleanly.
— Ali — Dolibarr AI Consultant / SiliconBlaze.com
1 Like
