Updating caused the database to reset (1.73.0 -> 1.78.1)
Hi, apologies if this is a duplicate. I wasn't able to find a similar issue here.
Like the title says, I attempted to update immich.
docker compose pull
was successful. docker compose up -d
initially gave me an error about insufficient permissions to stop a container, which later changed to "bind: address is already in use" when attempting to start immich-proxy. I (probably unwisely) killed the proxy service using sudo kill <pid>
, and docker compose up -d
then worked fine.
However, it appears immich either can't find the database or it disappeared. I was prompted to create a new admin account and none of my images, videos, settings or API keys are displayed (as if it were a fresh install). The images still do exist in my upload location.
What's my best course of action here? Should I do a bulk upload from the images that still exist, or is there a way to get my old database back?6 Replies
You probably did something that caused the
pgdata
volume (which holds the database data) to be deleted.
is there a way to get my old database back?Restore from your backups ;) Otherwise reuploading the library folder is the way to go. Make sure you don't accidentally upload the thumbnails etc
agh, that sucks because I don't really see anything that'd cause pgdata to be deleted. Well, since I don't have a backup (🧠) I'll reupload. Thank you!
You can use
docker volume ls
to check if it somehow still exists (but that seems unlikely)
It does seem to exist
Could be that's the newly created one of course 😅
aaah yeah that's likely.
Not a huge pain to reupload so I'll just do that then