The release notes for 0.19.4 mention that this version requires an upgrade to both pictrs and postgres, but there isn’t any information about what versions of those are supported. Is there someplace else I should be looking for this information? Or should I just YOLO with the latest version of each?
Well the join-lemmy.org docker-compose file reads
docker.io/postgres:16-alpine, and with your mention, I switched from version 15 to 16 but the postgres container errored with not being compatible with a version 15 initialized data directory.My instance has been running fine on v15 so far. (I switched back to 15 in the compose file and it works again)
Would be nice with lemmy documentation how to migrate from 15 to 16.
You need to export your DB and impirt it again. You can not simply upgrade. Switch back to v15 and make a dump.
Here is a little guide.
Pict-rs can be upgraded simply. Edit your docker-compose.yml and spin it up. After tge upgrade is complete, you can do the postgres upgrade
I successfully migrated postgres 15 to 16. I followed the general idea of the guide you posted, but I found it a little easier to do a slightly different process. Here’s what I did:
docker-compose downfor the lemmy instance
2. edit thedocker-compose.ymlfile and comment out all of the services except postgres. In addition, add a new volume to the postgres service that looks something like this:- ./volumes/miscfiles:/miscfiles- edit the
docker-compose.ymlfile and add a new volume to the postgres service that looks something like this:- ./volumes/miscfiles:/miscfiles docker-compose up -d postgres(this starts just thepostgresservice from the docker compose file)docker exec -it [container name] pg_dumpall -U [username] -f /miscfiles/pgdumpall20240628(I think this will work, but it’s not exactly what I did… rather, I randocker exec -it [container name] bash, and then ranpgdumpall -U [username] -f /miscfiles/pgdumpall20240628. The end result is a dumpall file saved in the./volumes/miscfilesdirectory on the host machine)docker-compose downmv ./volumes/postgres ./volumes/postgresBAK20240628(move your existing postgres data to a new directory for backup purposes)mkdir ./volumes/postgres(re-create an empty postgres data folder. make sure the owner and permissions match thepostgresBAK20240628directory)- edit the
docker-compose.ymland update the postgres image tag to the new version docker-compose up -d postgres(you’ll now have a brand new postgres container running with the new version)docker-exec -it [container name] psql -U [username] -f /miscfiles/pgdumpall20240628(again, I think this will work, but Ibashed in and ran the command from within the container. This also allows you to watch the file execute all of the commands… I don’t know if it will do that if you run it from the host.)docker-compose down
12. edit thedocker-compose.ymland un-comment all of the other services that you commented out in step 2docker-compose up -d
Hopefully that helps anyone that might need it!
edited to reflect the comment below
If you only want to start 1 service of your entire compose file just use the name in the service section. No need to comment out everything else. For Lemmy it would be:
docker compose up -d postgresThis will only start the postgres container of this stack. Glad you found a way which worked for you ☺️
ahhhh yes, that makes perfect sense… thank you for pointing that out! Especially since I’m not good enough with
vito know how to bulk delete the first character in specific lines, I had to manually arrow and delete.
AFAIK the only downside of still being on 15 is it doesn’t perform quite as well on high traffic instances but should otherwise be fine.
I looked about for it and the PG update basically involves creating a new folder to initialize and then exporting/importing the old DB, but haven’t successfully done so yet here.
Postgres 16 and pict-rs 0.5.16, but neither are critical it’ll just miss features. Like if you use pict-rs 0.4.x then you can’t use the image proxy, but you shouldn’t anyway.
Thank you, that’s super helpful!
