Portainer EE - Update stuck rebooting

[IzaacJ]

Ask a Question!

Updated portainer today, and all I get now is this in the log, and the container is constantly rebooting.

�[90m2024/09/20 10:59AM�[0m �[32mINF�[0m �[1mgithub.com/portainer/portainer-ee/api/database/boltdb/db.go:147�[0m�[36m >�[0m closing PortainerDB |
�[90m2024/09/20 10:59AM�[0m �[32mINF�[0m �[1mgithub.com/portainer/portainer-ee/api/datastore/backup.go:58�[0m�[36m >�[0m database restored | �[36mfrom=�[0m/data/backups/portainer.db.bak �[36mto=�[0m/data/portainer.db
�[90m2024/09/20 10:59AM�[0m �[32mINF�[0m �[1mgithub.com/portainer/portainer-ee/api/database/boltdb/db.go:125�[0m�[36m >�[0m loading PortainerDB | �[36mfilename=�[0mportainer.db
�[90m2024/09/20 10:59AM�[0m �[32mINF�[0m �[1mgithub.com/portainer/portainer-ee/api/datastore/backup.go:72�[0m�[36m >�[0m Restored database version: Portainer EE 2.18.4 |
�[90m2024/09/20 10:59AM�[0m �[32mINF�[0m �[1mgithub.com/portainer/portainer-ee/api/datastore/migrate_data.go:60�[0m�[36m >�[0m database restored to previous version |
�[90m2024/09/20 10:59AM�[0m �[1m�[31mFTL�[0m�[0m �[1mgithub.com/portainer/portainer-ee/api/cmd/portainer/main.go:196�[0m�[36m >�[0m failed migration | �[36merror=�[0m�[31m"failed to migrate database: failed in Always migrations returned error: failed rebuilding stack file system with version: failed to copy stack 13 project folder: failed to backup source directory: Target path already exists"�[0m �[36mstack_trace=�[0m[{"func":"(*Store).MigrateData","line":"52","source":"migrate_data.go"},{"func":"initDataStore","line":"194","source":"main.go"},{"func":"buildServer","line":"496","source":"main.go"},{"func":"main","line":"816","source":"main.go"},{"func":"main","line":"267","source":"proc.go"},{"func":"goexit","line":"1650","source":"asm_amd64.s"}]

No idea what I could do to resolve this, and the compose/13 folder only contains an empty ´v1´ folder. compose-backup is empty. I've tried to rename the backup db file with no success.

Any ideas?

EDIT: Managed to get it running by going back to the 2.18.4 image, which was the first image I pulled 14 months ago, the only other image I have was pulled 12 months ago, but that didn't work either, and ended up in a similar state as the latest as of now.

EDIT2: Was able to get it up and running with 2.19.0, but 2.19.1 image caused the same migration issue.