Planka (stack)
Open source Trello-like kanban board for project management built with React and Node.js
Services
planka
Configuration
Imageghcr.io/plankanban/planka:latest3000:1337/app/data : planka-dataBASE_URL=http://localhost:3000DATABASE_URL=postgresql://postgres@postgres/plankaSECRET_KEY=changeme-generate-a-long-random-secretunless-stoppedpostgres
Configuration
Imagepostgres:16-alpine/var/lib/postgresql/data : postgres-dataPOSTGRES_DB=plankaPOSTGRES_HOST_AUTH_METHOD=trustunless-stoppedImage details
Installation
- 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 the app you wish to deploy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Service #1 - planka
docker run -d --name planka \
-p 3000:1337 \
-e 'BASE_URL=http://localhost:3000' \
-e 'DATABASE_URL=postgresql://postgres@postgres/planka' \
-e 'SECRET_KEY=changeme-generate-a-long-random-secret' \
-v planka-data:/app/data \
--restart=unless-stopped \
ghcr.io/plankanban/planka:latestService #2 - postgres
docker run -d --name postgres \
-e 'POSTGRES_DB=planka' \
-e 'POSTGRES_HOST_AUTH_METHOD=trust' \
-v postgres-data:/var/lib/postgresql/data \
--restart=unless-stopped \
postgres:16-alpineIf the stack expects env vars, set them or add them to a .env file first.
version: "3"
services:
planka:
image: ghcr.io/plankanban/planka:latest
restart: unless-stopped
ports:
- "3000:1337"
environment:
- BASE_URL=http://localhost:3000
- DATABASE_URL=postgresql://postgres@postgres/planka
- SECRET_KEY=changeme-generate-a-long-random-secret
volumes:
- planka-data:/app/data
depends_on:
postgres:
condition: service_healthy
postgres:
image: postgres:16-alpine
restart: unless-stopped
environment:
- POSTGRES_DB=planka
- POSTGRES_HOST_AUTH_METHOD=trust
volumes:
- postgres-data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U postgres -d planka"]
interval: 10s
timeout: 5s
retries: 5
volumes:
planka-data:
postgres-data:
Or, use the original compose file, straight from the template repo. Deploy with:
git clone https://github.com/lissy93/portainer-templates
cd portainer-templates
docker compose -f sources/stacks/planka.yml up -dFor more installation options, see the Documentation in our GitHub repo
Container Documentation
postgres Documentation
The PostgreSQL object-relational database system provides reliability and data integrity.
Serve Planka (stack) on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying planka-stack.example.com to http://planka:1337
Add this to your Caddyfile
planka-stack.example.com {
reverse_proxy http://planka:1337
}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.
Port already in use
If deployment fails with "Bind for 0.0.0.0:3000 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :3000 - Stop the other service, or pick a different host port. In
3000:1337only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:3000. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, planka can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 3000
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/plankanban/planka:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "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 within planka's repo
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates