An Immich user on ZimaOS selected latest for the application image but saw the installed server remain on an older release. The discussion shows that an Immich update could involve at least two containers—server and machine learning—and that the correct path changed as both Immich and ZimaOS evolved.
This is a version-sensitive community history, not a timeless upgrade recipe. Early replies concern Immich 1.123–1.125 on ZimaOS 1.3.1-1; later official guidance describes ZimaOS 1.5.1 handling an upgrade from older Immich versions to version 2 and its database transition.
Why Selecting latest Was Not Enough in the Early Case
The original user had latest selected but did not receive a newer server image. Another participant reported being stuck on Immich 1.123. A community reply advised checking both the immich-server and immich-machine-learning image settings instead of changing only one service.
Participants also warned that the visible word latest did not consistently result in the image they expected. They experimented with explicit release tags, but the screenshots show that entering a tag did not resolve every ZimaOS 1.3.1-1 case.
Exact Tag Syntax Mattered, but It Was Not the Whole Story
One troubleshooting branch noticed that a manually entered version did not exactly match the published image tag. The responder directed users to the container tag list referenced in the thread and suggested using the same explicit version for both services before saving and restarting.
The author of that attempt reported that neither of the tag variations suggested in the replies completed the upgrade. That failed result is important: the thread does not support presenting a particular 1.125 tag as a universal solution for the older app package.
Later Users Updated Both Containers to Immich 2.2.3
In November 2025, a participant running Immich 2.1.0 reported that latest still failed. Manually selecting version 2.2.3 for both the machine-learning and server containers succeeded for that user, and another participant confirmed the same paired change worked in their installation.
Zima team member Giorgio added a separate version boundary: in ZimaOS 1.5.1, the Immich app could be upgraded from older versions to version 2, with ZimaOS handling the database issue in the background after the update button was selected. That official statement applies to the later 1.5.1 workflow, not to the 1.3.1-1 screenshots from the start of the thread.
Large Version Jumps May Need Their Own Migration Path
A May 2026 reply stated that very old Immich installations may need to move through smaller updates rather than jump directly to the newest release. The thread does not provide a tested sequence of every intermediate version, so that comment is preserved as community advice rather than a verified migration matrix.
The combined lesson from the thread is to identify the ZimaOS release, current Immich version, image source, and tags for both paired services before changing anything. A fix reported for a minor 2.x update should not automatically be applied to a much older 1.x database migration.
FAQ
Do the Immich server and machine-learning tags need attention together?
Yes in the successful paired-update reports. Users changed both services to the same target release rather than updating only the server container.
Does the latest tag guarantee that ZimaOS will install the newest Immich release?
Not in this thread. Multiple users reported that latest left them on an older version, while explicit tags worked only in some later cases.
Can guidance for ZimaOS 1.5.1 be applied to the 1.3.1-1 case?
No. The 1.5.1 reply explicitly describes newer support for upgrading older Immich installations across the version 2 database transition. The earlier screenshots document a different app and OS state.
