The Umami upgrade that fails ends the same way: the container boots, stops, and the log says A migration failed to apply. New migrations cannot be applied before the error is recovered from (Prisma P3018) or migrate found failed migrations in the target database (P3009). Seven GitHub issues between August 2022 and May 2025 are that message, on Postgres and on MariaDB, and the threads point to the same things to look at before you pull the new image. Five checks, each one you can start in a minute:
1. Do you already have a half-applied migration? A failed migration blocks every later one, so a database that has one will fail the next upgrade at once. In the database Umami uses:
SELECT migration_name , started_at , finished_at , rolled_back_at FROM _prisma_migrations WHERE finished_at IS NULL AND rolled_back_at IS NULL ;
Enter fullscreen mode
Exit fullscreen mode
Any row means a migration started, did not finish and was not rolled back. Fix that first (check 5), not after the upgrade.
2.…