Repository navigation
v1.5.1 — Docker migration fix
FreeToPlay 1.5.1 — Docker migration fix
What went wrong
Publishing historical 1.0–1.4 release tags rebuilt old Docker images. Force Update could pull an early image that still had the obsolete init migration, which crashes against an existing database (table User already exists / P3009).
Fixed
- Docker images now build only from
main(not from old release tags) latestandv1.5.1always match the current app- Clearer startup error if migrations fail
Recover your Unraid container NOW
- Stop FreeToPlay
- In Unraid terminal:
rm -f /mnt/user/appdata/freetoplay/data/prod.db
rm -f /mnt/user/appdata/freetoplay/data/prod.db-journal- Set Repository to:
ghcr.io/mckenna654/freetoplay:latest - Wait for the GitHub Action to finish, then Force Update and start
This wipes session data in the DB (expected after a broken migration). Discord login will recreate users as people sign in.