EspoCRM
Stack
CRM for keeping track of customers and sales: accounts, contacts, leads, opportunities, cases, meetings and calls, with a shared calendar, email inbox, reports and a no-code entity builder. Source: https://github.com/espocrm/espocrm
Source details
Configuration
TypeComposelinuxESPOCRM_ADMIN_PASSWORD=''ESPOCRM_DB_PASSWORD=''ESPOCRM_PORT=8680ESPOCRM_URL=http://localhost:8680unless-stoppedTemplate by NotAFlightRisk·Source
Report issueNotes
openssl rand -hex 16 makes a good one), since the stack won't start without them, and keep the database password the same when you redeploy. The first start takes a minute while it sets up the database. Then open http://<your-host>:8680 (or whichever port you picked) and log in as admin with your password. There are no sign-ups, you add everyone else under Administration --> Users. Put the address you'll actually type in the browser in the address field too, since links in emails and password resets use it, and they point at localhost until you do. It's set from the stack on every start, so to change it later edit the address in the stack's environment variables and redeploy, rather than in Settings. Nothing gets emailed until you add an SMTP server under Administration --> Outbound Emails. The daemon container runs the scheduled jobs (fetching email, reminders, clean-up), so leave it running. The Administration page shows a news panel from espocrm.com, which gets told your version and address, and a scheduled job asks espocrm.com for the latest version. To update, redeploy with the image re-pulled and it upgrades the database on start. Uploads and settings live in the espocrm-data volume, extensions and customisations in espocrm-custom and espocrm-client-custom, and your records in db-data. Docs: docs.espocrm.comServices
espocrm
Configuration
Imageespocrm/espocrm:10${ESPOCRM_PORT:-8680}:80/var/www/html/data : espocrm-data/var/www/html/custom : espocrm-custom/var/www/html/client/custom : espocrm-client-customESPOCRM_DATABASE_PLATFORM=MysqlESPOCRM_DATABASE_HOST=dbESPOCRM_DATABASE_NAME=espocrmESPOCRM_DATABASE_USER=espocrmESPOCRM_DATABASE_PASSWORD=${ESPOCRM_DB_PASSWORD:?Set a database password}ESPOCRM_ADMIN_USERNAME=adminESPOCRM_ADMIN_PASSWORD=${ESPOCRM_ADMIN_PASSWORD:?Set an admin password}ESPOCRM_SITE_URL=${ESPOCRM_URL:-http://localhost:8680}ESPOCRM_CONFIG_SITE_URL=${ESPOCRM_URL:-http://localhost:8680}unless-stoppedImage details
daemon
Configuration
Imageespocrm/espocrm:10docker-daemon.sh/var/www/html/data : espocrm-data/var/www/html/custom : espocrm-custom/var/www/html/client/custom : espocrm-client-customunless-stoppedImage details
db
Configuration
Imagemariadb:11.4/var/lib/mysql : db-dataMARIADB_DATABASE=espocrmMARIADB_USER=espocrmMARIADB_PASSWORD=${ESPOCRM_DB_PASSWORD:?Set a database password}MARIADB_RANDOM_ROOT_PASSWORD=1unless-stoppedImage details
Standalone Install
Select an install method, to see config/commands for deploying EspoCRM
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select EspoCRM, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
espocrm:
image: espocrm/espocrm:10
restart: unless-stopped
ports:
- "${ESPOCRM_PORT:-8680}:80"
environment:
ESPOCRM_DATABASE_PLATFORM: Mysql
ESPOCRM_DATABASE_HOST: db
ESPOCRM_DATABASE_NAME: espocrm
ESPOCRM_DATABASE_USER: espocrm
ESPOCRM_DATABASE_PASSWORD: ${ESPOCRM_DB_PASSWORD:?Set a database password}
ESPOCRM_ADMIN_USERNAME: admin
ESPOCRM_ADMIN_PASSWORD: ${ESPOCRM_ADMIN_PASSWORD:?Set an admin password}
ESPOCRM_SITE_URL: ${ESPOCRM_URL:-http://localhost:8680}
ESPOCRM_CONFIG_SITE_URL: ${ESPOCRM_URL:-http://localhost:8680}
volumes:
- espocrm-data:/var/www/html/data
- espocrm-custom:/var/www/html/custom
- espocrm-client-custom:/var/www/html/client/custom
depends_on:
db:
condition: service_healthy
daemon:
image: espocrm/espocrm:10
restart: unless-stopped
entrypoint: docker-daemon.sh
volumes:
- espocrm-data:/var/www/html/data
- espocrm-custom:/var/www/html/custom
- espocrm-client-custom:/var/www/html/client/custom
depends_on:
- espocrm
db:
image: mariadb:11.4
restart: unless-stopped
environment:
MARIADB_DATABASE: espocrm
MARIADB_USER: espocrm
MARIADB_PASSWORD: ${ESPOCRM_DB_PASSWORD:?Set a database password}
MARIADB_RANDOM_ROOT_PASSWORD: "1"
volumes:
- db-data:/var/lib/mysql
healthcheck:
test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]
interval: 5s
timeout: 5s
retries: 20
volumes:
espocrm-data:
espocrm-custom:
espocrm-client-custom:
db-data:
Or deploy it directly from the source:
git clone https://github.com/NotAFlightRisk/portainer-templates-extras
cd portainer-templates-extras
docker compose -f apps/espocrm/compose.yml up -dMore install options in our documentation, or see espocrm/espocrm for app-specific guidance.
Container Documentation
espocrm Documentation
LEGACY. Use the Docker Official Image: hub.docker.com/_/espocrm
daemon Documentation
LEGACY. Use the Docker Official Image: hub.docker.com/_/espocrm
db Documentation
MariaDB Server is a high performing open source relational database, forked from MySQL.
Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Image won't pull
Test the pull directly on the host: docker pull espocrm/espocrm:10
- "manifest unknown" means the tag no longer exists.
- "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on espocrm/espocrm
- Template not working: Open an issue on NotAFlightRisk/portainer-templates-extras
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
EspoCRM is a Compose stack, a set of containers (3 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.
The services
This stack is built from 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
espocrmrunsespocrm/espocrm:10, starts after dbdaemonrunsespocrm/espocrm:10, starts after espocrmdbrunsmariadb:11.4
Volumes
A volume is where EspoCRM keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/var/www/html/datakept in theespocrm-datavolume Docker manages/var/www/html/customkept in theespocrm-customvolume Docker manages/var/www/html/client/customkept in theespocrm-client-customvolume Docker manages/var/lib/mysqlkept in thedb-datavolume Docker manages
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. EspoCRM takes 13 of them, and 3 need a value before it'll start properly:
ESPOCRM_DATABASE_PLATFORM, defaults toMysqlESPOCRM_DATABASE_HOST, defaults todbESPOCRM_DATABASE_NAME, defaults toespocrmESPOCRM_DATABASE_USER, defaults toespocrmESPOCRM_DATABASE_PASSWORD, needs a valueESPOCRM_ADMIN_USERNAME, defaults toadminESPOCRM_ADMIN_PASSWORD, needs a valueESPOCRM_SITE_URL, defaults tohttp://localhost:8680ESPOCRM_CONFIG_SITE_URL, defaults tohttp://localhost:8680MARIADB_DATABASE, defaults toespocrmMARIADB_USER, defaults toespocrmMARIADB_PASSWORD, needs a valueMARIADB_RANDOM_ROOT_PASSWORD, defaults to1
Restart policy
The restart policy here is unless-stopped, so Docker restarts EspoCRM after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Portainer puts these services on one shared private network, so they can find each other by name (like espocrm) while only the ports above are open to you.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
EspoCRM is open source, released under the AGPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set EspoCRM up. Add the template list to Portainer once, then deploying EspoCRM is a click rather than a wall of config.