Leantime is an open source project management system for small teams and startups written in PHP, Javascript using MySQL. https://leantime.io
This is the official Docker image for Leantime. It was built using the latest Leantime release.
Below you will find examples on how to get started with Leantime trough docker run or docker compose.
git clone https://github.com/Leantime/docker-leantime.git
cd docker-leantime
cp sample.env .env
Edit .env file with your settings and then run
docker compose up -d
docker network create leantime-net
docker run -d --restart unless-stopped -p 3306:3306 --network leantime-net \
-e MYSQL_ROOT_PASSWORD= changeme123 \
-e MYSQL_DATABASE=leant ime \
-e MYSQL_USER=lean \
-e MYSQL_PASSWORD=chang eme123 \
--name mysql_leantime mysql:8.4
By default, Leantime runs on port 8080 internally.
To map port 80 externally to 8080 internally in docker-compose.yml:
ports: - "80:8080"
The published image runs as uid/gid 1000. PUID and PGID are build arguments, so setting them as environment variables on the published image has no effect.
Anything you mount into the container (named volumes or bind mounts) must be writable by the uid the container runs as. You have two options:
Keep uid 1000 and hand your bind-mounted host folders to it:
sudo chown -R 1000:1000 ./userfiles ./public_userfiles ./plugins ./logs
sudo chmod -R 775 ./userfiles ./public_userfiles ./plugins ./logs
Run as your own uid (Synology, Unraid, TrueNAS, rootless podman). Set user: with group 0; the image's writable folders are group-owned by root for this. Find your ids with id username on the host:
services:
leantime:
user: "1026:0" # Replace 1026 with your host user ID
Or with docker run: docker run --user "$(id -u):0" ... leantime/leantime:latest.
To bake a different default uid into the image instead, build it yourself: docker build --build-arg PUID=1026 --build-arg PGID=100 --build-arg LEAN_VERSION=<version> .
Important directories that should be persisted:
volumes:
- public_userfiles:/var/www/html/public/userfiles # Public files, logos
- userfiles:/var/www/html/userfiles # User uploaded files
- plugins:/var/www/html/app/Plugins # Plugin directory
- logs:/var/www/html/storage/logs # Application logs
As an alternative to passing sensitive information via environment variables, _FILE may be appended to the environment variables listed below, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in /run/secrets/<secret_name> files. For example:
docker run -d --restart unless-stopped -p 80:80 --network leantime-net \
-e LEAN_DB_HOST=mysql_leantime \
-e LEAN_DB_USER=admin \
-e LEAN_DB_PASSWORD_FILE=/run/secrets/lean-db-password \
-e LEAN_DB_DATABASE=leantime \
--name leantime leantime/leantime:latest
Currently, this is only supported for LEAN_DB_PASSWORD, LEAN_EMAIL_SMTP_PASSWORD, LEAN_S3_SECRET, and LEAN_SESSION_PASSWORD.
If you see "Operation not permitted" or "Permission denied" errors, the mounted folders aren't writable by the uid the container runs as (see Running as Non-Root User).
For bind mounts, fix ownership on the host (see above). For named volumes, fix them from inside the container. The container runs as a non-root user, so docker exec needs -u root:
docker exec -u root leantime chown -R www-data:0 /var/www/html/userfiles \
/var/www/html/public/userfiles \
/var/www/html/storage/logs \
/var/www/html/app/Plugins
docker exec -u root leantime chmod -R ug+rwX /var/www/html/userfiles \
/var/www/html/public/userfiles \
/var/www/html/storage/logs \
/var/www/html/app/Plugins
On Synology, also check that the host folders show no + (DSM ACL) in ls -la. Running chmod on the host folder removes it.
dependency failed to start: container mysql_leantime is unhealthy on the very first docker compose up usually means MySQL is still initializing its data directory. On NAS HDD arrays this can take several minutes (we measured about 3 minutes on a Synology with SSD cache). The compose file's healthcheck allows a 300 second start_period for this. If your storage is slower still, raise start_period. Later restarts are fast.
- Verify database credentials in .env file
- Ensure database container is running and healthy
- Check network connectivity between containers
- Ensure the plugins volume is properly mounted
- Check write permissions on the plugins directory
- Verify plugin compatibility with your Leantime version
- Check logs:
docker logs leantime - Verify port mappings
- Ensure no conflicts with host ports
See sample.env for all available options. Critical variables:
LEAN_DB_HOST=mysql_leantime
LEAN_DB_USER=lean
LEAN_DB_PASSWORD=changeme123
LEAN_DB_DATABASE=leantime
LEAN_SESSION_PASSWORD=your_secure_password
- Always change default passwords
- Use Docker secrets for sensitive data
- Consider running as non-root user
- Enable HTTPS in production
- Restrict network access appropriately