Questions about valkey and postgres

[vmfleungapps-spec]

Hi all, started using Immich about 5 to 6 months ago, basically work fine on my Ugreen DXP2800. Recently, start checking the docker app on native UGOS and found out some msg about postgres and valkey, either saying some error on image for both of them. That said, seems the whole immich service is fine, can access them, search, add photos etc. Looking at the docker compose yaml and noticed some diff in my version against the sample yaml from immich on "image" statement of the respective service. So updated those 2 "image" statements on yaml and redeployed, the errors on these 2 images still around from the UGOS docker apps perspective, and as before, the whole service is fine. Here are the 2 statements : "image: docker.io/valkey/valkey:9@sha256:8e8d64b405ce18f41b8e5ee20aa4687a8ed0022d1298f2ce31cdcf3a76e09411
image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23"
Questions :

1. Any idea about what is going on the "error" showing on the docker app?
2. If I am not wrong, the latest postgres version being used by immich is 16? Should I get a more updated version for the progres datatbase image? Any impact of losing what I have up and running now? Or should I take some sort of migration steps after upgrading to a new version?
   Thanks for your help in advance. I am not that tech savvy, so pls bear with me. If it is not appropriate to ask these kind of questions here, pls let me know. Thanks.

[tigran-sargsyan-w]

I would not upgrade PostgreSQL to 16 just because PostgreSQL 16 is newer.

The important thing here is to follow the database image from the Immich release you are actually running. The current official Immich Compose configuration still uses a PostgreSQL 14 based image:

image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:...

and Valkey is also pinned to a specific image/digest.

So those versions are intentional dependencies, not simply outdated containers.

A PostgreSQL major-version upgrade is also not the same as updating a normal application container. You should not change:

postgres:14 -> postgres:16

while reusing the same data directory unless you follow a proper PostgreSQL migration procedure (pg_upgrade or dump/restore).

Since Immich itself is working correctly, I would:

1. Restore the exact Valkey and PostgreSQL images from the official Compose file for your Immich release.
2. Check docker compose ps and the container health status.
3. Treat the UGOS "image error" separately from the Immich application if both containers are healthy.
4. Upgrade dependencies only when the Immich release/upgrade documentation changes them.

In short: I would keep PostgreSQL 14 here. Do not manually move to PostgreSQL 16 just because a newer major version exists.

The same principle applies to Valkey: use the image pinned by the Immich release rather than independently tracking the newest tag.

[vmfleungapps-spec]

Thanks mate. Checked my yaml, postgres is the same as the official one, valkey is diff, think I changed then a while back when playing around with tailscale tsdproxy. Have changed back to the one in official yaml, that said, the "error" msg on UGOS is still there for both image. Immich still working as usual, hopefully nothing will break. Thanks again

[tigran-sargsyan-w]

Thanks mate, I’ll definitely check it out!

And if my answer helped, I’d really appreciate it if you could mark it as the accepted answer. Thanks!