mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
[Bug]: Cannot install #854
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @daniebker on GitHub (Nov 4, 2025).
Where is the problem occurring?
I encountered the problem while interacting with the server (Backend)
What browsers are you seeing the problem on?
Other
Current behavior
Following the instructions in the production docs
I get the following issue:
Desired behavior
running
docker compose run --rm planka npm run db:create-admin-usershould bootstrap the database with the admin user.Steps to reproduce
Follow the steps in the production docs
Other information
I’m running docker in a ubuntu server. I have other applications working fine.
@jansenfuller commented on GitHub (Jan 14, 2026):
I am having this issue as well but on k3s. Deployed using the k3s Helm controller with the following configuration. I was moving from a previous deployment on a docker container in Ubuntu VM on Proxmox. DB was on a Proxmox LXC running Alpine Linux.
Here is the coresponding output
@meltyshev commented on GitHub (Jan 14, 2026):
Hey! This error means the database was already initialized with v1, but v2 uses a different set of migration files - because of that, the app can't find the migrations that were already applied.
To upgrade the database, there's an upgrade script included that should resolve the migration issues and also update all existing data and files.
For a Docker-based installation, you can follow this guide: https://docs.planka.cloud/docs/upgrade-to-v2/docker/
I'm not very familiar with k3s, but this comment might be helpful: https://github.com/plankanban/planka/issues/1144#issuecomment-2926243544
UPD: please don't forget to make a full backup before running the upgrade script.
@jansenfuller commented on GitHub (Jan 15, 2026):
I forgot to run a backup but that command from #1144 did the trick! I am up and running again. Thank you very much for your help.
For future reference the command is
and worked with k8s version 1.34.3+k3s1.