vectorchord version in docker-compose.yml
I followed the steps in 1.133.0 https://github.com/immich-app/immich/releases/tag/v1.133.0 and changed my docker-compose.yml to switch the db to
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
and everything has been running fine.
I use what'supdocker to monitor my docker images to see if I missed a notice about updates and saw that immich_postgress is outdated even though I've been keeping up with my immich updates.
I looked at the latest docker-compose.yml
https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml
and saw that the version of postgres is now
image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:32324a2f41df5de9efe1af166b7008c3f55646f8d0e00d9550c16c9822366b4a
I typically read through the changes, make any adjustments recommended and run docker compose pull && docker compose up -d
Should I be manually updating my docker-compose.yml to match the differences I'm seeing?
13 Replies
:wave: Hey @beardytravis,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:files attached
Any advice on if I can just sub in the newer version of vectorchord?
Final bump to see if I can get an answer. If not I'll make a backup this weekend and give it a go and report back.
you can use 14-vectorchord0.4.3
you shouldn't need pgvectors0.2.0
you said you are on 1.133, you should be on a newer version likely
go to 1.142 first then upgrade the PG image
I'm currently on 1.141.1, but 1.133 was when I followed the instructions to switch to vectorchord and haven't changed the vectorchord version since.
So upgrade to 1.142, then stop the container and change the db image from
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
to
image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:32324a2f41df5de9efe1af166b7008c3f55646f8d0e00d9550c16c9822366b4a
and I should be OK?
I think this is all my error. I've been ignoring the comment at the top of the docker-compose.yml to
I've been reading the release notes and updating my docker-compose.yml with incremental changes, but not pulling the latest version each time.
I was making an assumption that running the pull is good enough to update everything unless it's called out specifically in the release notes.
I'm confused about this statement though. What do you mean that I don't need pgvectors0.2.0?
pgvectors is not used anymore by Immich.
These images get constant updates, please don't bother with using a watchdog on them
also, like Finn said, pgvectors is deprecated, you can move to
postgres:14-vectorchord0.4.3I'm confused then because
image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0 is what's in the docker-compose.yml for 1.142.1
https://github.com/immich-app/immich/releases/download/v1.142.1/docker-compose.ymlYes, that's to prevent people from messing up because you need both extensions during migration
Got it. So since I've already migrated when I updated to 1.133.0 and used
image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0 then I can remove the -pgvectors0.2.0... moving forward?Yep
Whelp, I screwed something up. Just lost all the folders under immich/library. Good thing they're all backed up. Now I just need to figure out how to restore them from backup.
rsync and Truenas FTW. back up and running on v1.142.1 with the corrected DB image
This thread has been closed. To re-open, use the button below.