I have nextcloud-aio running in docker and recently did an update to all of the containers without thinking much about it. Per logs, it isn’t starting because the postgresql database files were for version 16 and not compatible with 17.5. I was dumb and didn’t follow or even know about the migration guide by doing a dump first. How do I recover? Or do I have to start over? I was hoping I could just create a new container with the older image and keep all paths and variables the same.
I tried different tags but only latest seemed to work.
Ouch, easy mistake to make You should be able to recover by spinning up a Postgres 16 container and pointing it to your existing data directory. Keep all paths/volumes the same. Once it’s running, dump the DB, then upgrade to 17 and restore the dump.
Let me know if you need help with the docker commands.
I tried that but couldn’t get it to work. Probably missing scripts or certain parameters. The postgresql version I had was installed using the nextcloud-aio stack. I tried to copy all parameters over but couldn’t get it to properly start. I’m pretty new to docker so forgive me for being a total noob.
I was hoping I could just modify the pull link to a variant of version 16 instead of :latest but that didn’t work. If there was a path to a previous version, that would be the easiest route I think.
Yeah, I think that is something I’ll have to do. Delete containers, remake and restore the backup. Fortunately, files are all still good. Was just hoping I could change the postgresql container and have it functioning again.
You should be able to recover by spinning up a Postgres 16 container and pointing it to your existing data directory. Keep all paths/volumes the same. Once it’s running, dump the DB, then upgrade to 17 and restore the dump.