Koillection
Stack
Koillection is a self-hosted collection manager created to keep track of physical (mostly) collections of any kind like books, DVDs, stamps, games..
Services
koillection
Configuration
Imagekoillection/koillection:dev181:80/var/www/koillection/public/uploads : /portainer/Files/AppData/Config/koillection/public/uploads/var/www/koillection : /portainer/Files/AppData/Config/koillectionAPP_ENV=devAPP_DEBUG=1DB_DRIVER=pdo_pgsqlDB_NAME=koillectionDB_HOST=postgresqlDB_PORT=25432DB_USER=postgresDB_PASSWORD=passwordDB_VERSION=14PHP_TZ=Europe/AthensHTTPS_ENABLED=0alwaysImage details
postgresql
Configuration
Imagepostgres:1425432:5432/var/lib/postgresql/data : /portainer/Files/AppData/Config/postgresqlPOSTGRES_DB=koillectionPOSTGRES_USER=postgresPOSTGRES_PASSWORD=passwordPOSTGRES_HOST_AUTH_METHOD=trustImage details
koinmysql
Configuration
Imagemysql:latest--default-authentication-plugin=mysql_native_password43306:3306/var/lib/mysql : /portainer/Files/AppData/Config/koillection/koinmysqlMYSQL_ROOT_PASSWORD=passwordMYSQL_DATABASE=koillectionImage details
Standalone Install
Select an install method, to see config/commands for deploying Koillection
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 Koillection, 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:
#FPM image
koillection:
container_name: koillection
image: koillection/koillection:dev
restart: always
ports:
- 181:80
environment:
- APP_ENV=dev
- APP_DEBUG=1
- DB_DRIVER=pdo_pgsql
- DB_NAME=koillection
- DB_HOST=postgresql
- DB_PORT=25432
- DB_USER=postgres
- DB_PASSWORD=password
- DB_VERSION=14
- PHP_TZ=Europe/Athens
- HTTPS_ENABLED=0
depends_on:
- koinmysql
- postgresql
volumes:
- /portainer/Files/AppData/Config/koillection/public/uploads:/var/www/koillection/public/uploads
- /portainer/Files/AppData/Config/koillection:/var/www/koillection
postgresql:
container_name: postgresql
image: postgres:14
environment:
- POSTGRES_DB=koillection
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=password
- POSTGRES_HOST_AUTH_METHOD=trust
ports:
- 25432:5432
volumes:
- /portainer/Files/AppData/Config/postgresql:/var/lib/postgresql/data
koinmysql:
container_name: mysql
image: mysql:latest
command: --default-authentication-plugin=mysql_native_password
environment:
- MYSQL_ROOT_PASSWORD=password
- MYSQL_DATABASE=koillection
ports:
- 43306:3306
volumes:
- /portainer/Files/AppData/Config/koillection/koinmysql:/var/lib/mysql
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/koillection.yml up -dMore install options in our documentation.
Container Documentation
koillection Documentation
Koillection is a self-hosted service allowing users to manage any kind of collections.
postgresql Documentation
The PostgreSQL object-relational database system provides reliability and data integrity.
koinmysql Documentation
MySQL is a widely used, open-source relational database management system (RDBMS).
Serve Koillection 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 koillection.example.com to http://koillection:80
Add this to your Caddyfile
koillection.example.com {
reverse_proxy http://koillection:80
}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:181 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :181 - Stop the other service, or pick a different host port. In
181:80only 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:181. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, Koillection can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 181
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Config/koillection/public/uploads(and the same for the other mapped folders)
Image won't pull
Test the pull directly on the host: docker pull koillection/koillection:dev
- "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 always 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 Koillection's repo
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Koillection 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:
koillectionrunskoillection/koillection:dev, starts after koinmysql, postgresqlpostgresqlrunspostgres:14koinmysqlrunsmysql:latest
Ports
A port is the door the app answers on. A mapping like 181:80 means it's reachable on port 181 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:181 in a browser. It opens:
181:80, likely the web interface25432:543243306:3306
Volumes
A volume is where Koillection 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/koillection/public/uploadsfrom/portainer/Files/AppData/Config/koillection/public/uploadson the host/var/www/koillectionfrom/portainer/Files/AppData/Config/koillectionon the host/var/lib/postgresql/datafrom/portainer/Files/AppData/Config/postgresqlon the host/var/lib/mysqlfrom/portainer/Files/AppData/Config/koillection/koinmysqlon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Koillection takes 17 of them, all with defaults you can leave alone or tweak:
APP_ENV, defaults todevAPP_DEBUG, defaults to1DB_DRIVER, defaults topdo_pgsqlDB_NAME, defaults tokoillectionDB_HOST, defaults topostgresqlDB_PORT, defaults to25432DB_USER, defaults topostgresDB_PASSWORD, defaults topasswordDB_VERSION, defaults to14PHP_TZ, defaults toEurope/AthensHTTPS_ENABLED, defaults to0POSTGRES_DB, defaults tokoillectionPOSTGRES_USER, defaults topostgresPOSTGRES_PASSWORD, defaults topasswordPOSTGRES_HOST_AUTH_METHOD, defaults totrustMYSQL_ROOT_PASSWORD, defaults topasswordMYSQL_DATABASE, defaults tokoillection
Restart policy
The restart policy here is always, so Docker brings Koillection back up after a crash and again when the server reboots. Good for anything you want running around the clock. 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 koillection) 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.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Koillection up. Add the template list to Portainer once, then deploying Koillection is a click rather than a wall of config.