Change postgres and redis image version possible?
Hello, is it possible to change the image version of postgres and redis to the new image in the current docker compose example without problems, since there seems to be frixed versions in the compose wich do not automatically update? Do i need to take any additional steps, like a migration or can i just pull the new image? Thank you in advance for any help!
8 Replies
:wave: Hey @Xantha,
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. :blue_square: 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. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.I'm using the latest redis without issues, since I have a unique shared instance
as for pg, I would recommend to keep the proposed version, unless you know what you are doing, then pg16 with pgvecto extensions is supported from what I know
I am currently using these images for the database: image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0 and for redis
docker.io/redis:6.2-alpine@sha256:eaba718fecd1196d88533de7ba49bf903ad33664a92debb24660a922ecd9cac8
We’re sticking to valkey with the next release I think so I would wait for that
You can remove the @sha256:….. for each image but the first part should stay the same
ah, okay , so for now i can just keep this as is. thank you. the the current db verison is still the same. the redis seems to be docker.io/valkey/valkey:8-bookworm whereas i am on alpine
So if i change if i wait for the next release and change the image to the valkey image, there are no steps i need to take to migrate or so? this is only the case when the dm image changes?
No steps for valkey, you could do it now
8-alpine.. should work too. I’ll bring that up
Okay, that's nice and easy then. Thank you immich Team for the good work🙂
Apparently in testing the performance was better for bookworm but alpine should still work fine