v3.0.0 | Immich | Page 1

thick pulsar May 30, 2026, 9:12 PM

#

Hello, my Android app from Immich told me that the Android app has a new version, v2.7.5, and the app was still on v2.7.4. Version 2.7.5 wasn't yet available in the Play Store, so I had to get it from GitHub. However, the app there also said that it wasn't compatible with the server version. When I checked my server, I found that it was running version v3.0.0, and this version wasn't listed anywhere.

sage troutBOT May 30, 2026, 9:12 PM

#

:wave: Hey @thick pulsar,

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...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:ballot_box_with_check: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:blue_square: uploaded the relevant information (see below).
: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.

storm sigil May 30, 2026, 9:14 PM

#

Where on github did you download it?

thick pulsar May 30, 2026, 9:14 PM

#

today

storm sigil May 30, 2026, 9:14 PM

#

where, not when

thick pulsar May 30, 2026, 9:15 PM

#

sorry, the official Github repo

#

storm sigil May 30, 2026, 9:17 PM

#

Can you post the info requested by the bot please

thick pulsar May 30, 2026, 9:21 PM

#

👍

#

I can provide most of that, but my actual question is whether server version v3.0.0 exists.

wet oak May 30, 2026, 9:24 PM

#

it doesn't

#

not unless you are running the main branch off github or a dev preview

thick pulsar May 30, 2026, 9:25 PM

#

but i can get it?

wet oak May 30, 2026, 9:25 PM

#

no

thick pulsar May 30, 2026, 9:25 PM

#

well

#

my server told me i had v3.0.0

wet oak May 30, 2026, 9:26 PM

#

are you using a LLM?

thick pulsar May 30, 2026, 9:27 PM

#

in what way?

wet oak May 30, 2026, 9:27 PM

#

it's a pretty simple question. not really interested in arguing lol

#

if you ended up with version 3, you are being very ill advised, especially since it doesn't actually exist yet as a stable codebase

#

you can start over here

sage troutBOT May 30, 2026, 9:27 PM

#

https://immich.app/docs/install/docker-compose

thick pulsar May 30, 2026, 9:28 PM

#

sorry, i am german so my english skills are not that good

wet oak May 30, 2026, 9:29 PM

#

yeah, that's a dev preview. why are you using that

thick pulsar May 30, 2026, 9:36 PM

#

To be perfectly honest, I'm trying to understand this myself. For context, I'm not using AI in the sense that it sets everything up for me and I just have to plug and play. Of course, I'm looking into it myself, but I only came across the software through AI. And, um, I recently had the following problem: due to hardware issues, my SSD died, and I had to reinstall the server and, of course, reinstall the image because the overlay2 folder) and the image folder were pretty messed up. And I can say with 100% certainty that the environment file didn't come from AI; I used the environment file that was linked on GitHub. I just modified it a bit because version 2.7.5 or something like that wasn't working for me, so I simply added "Latest," meaning the last known image.

#

so v3.0.0 is not publicly available right now?

wet oak May 30, 2026, 9:41 PM

#

No. you should install according to our documentation as linked above

storm sigil May 30, 2026, 9:45 PM

#

Do you mean you went to the container image page and picked the newest entry? Because Immich doesn’t have a :latest tag

thick pulsar May 30, 2026, 9:58 PM

#

I've been thinking for a really long time about how to answer this question, and unfortunately, I can't say. I've searched through .env files that I downloaded from the official GitHub, and every AI chat from the last few days, but I couldn't find anything. I understand if you want answers, but I really can't say.

#

Since I use Portainer, I can see all the environment entries of the image in the "image" tab, such as IMMICH_SOURCE_URL, i.e., where this image comes from.

thick pulsar May 30, 2026, 10:30 PM

#

I checked again, and I also looked at the Bash history of my Docker Host system. I noticed that on May 26th, when I wanted to reinstall the image, I deleted all the immich server tags and also deleted this commit tag without thinking anything of it, because it was just there, so to speak. Then, presumably, I simply reinstalled the image with the release tag or something similar, and that's probably when this tag got included. I suspect this is just a guess. I suspect this because I previously had a Docker container, What's Up Docker, that updated all my images whenever an update was available. Unfortunately, I no longer have that container. Consequently, I also no longer have the logs for it. But I suspect that it was searching for the default, let's say, latest version, and didn't find a latest tag for this software, for this image, and probably just looked for the newest commit available. But I'm not 100% sure about that, because this commit I've presented here, V3.0.0, isn't normally found anywhere. But that's my only guess as to how it got there.

thick pulsar May 30, 2026, 11:00 PM

#

@storm sigil @wet oak I noticed that my Immich installation pulled a container image that does not appear to be from an official release, but rather from a merge request build.

Observation:
The image contains the following metadata:

IMMICH_SOURCE_REF=28553/merge

IMMICH_SOURCE_COMMIT=70ca3025b97b269c38cf939ab427d48e8c039d1e

IMMICH_SOURCE_URL=https://github.com/immich-app/immich/commit/70ca3025b97b269c38cf939ab427d48e8c039d1e

Created: 2026-05-26T20:23:29Z

This suggests the container was built from a CI pipeline of merge request 28553/merge.

What happened:

Around May 26, WUD (What's Up Docker) reported a new Immich image.

The image was automatically pulled and deployed.

Only afterward did it become clear that this was not a regular release image.

Assumption:
Tools like WUD detect newer images regardless of whether they are official releases or CI/merge builds, which can lead to unintentionally deploying non-release builds.

Questions:

Is it intentional that merge request / CI builds are published in the registry in a way that tools like WUD detect them as updates?

Are there recommended ways to distinguish or filter these builds from stable release images?

Would it make sense to separate or label these images more clearly?

This is meant as a technical observation to better understand how these images are intended to be consumed and how to avoid this situation.

icy ingot May 31, 2026, 1:24 AM

#

Not sure how "What's Up Docker" operate, usually for docker, you specific a tag i.e in this case release tag and when there is a new version available, you can pull the same tag to get it update

#

My guess is that "What's Up Docker" is configued somehow to pull the main tag instead

thick pulsar May 31, 2026, 9:36 AM

#

I had What's Up Docker enabled. In the "v3.0.0" image, I found IMMICH_SOURCE_REF=28553/merge and IMMICH_SOURCE_COMMIT=70ca3025b97b269c38cf939ab427d48e8c039d1e. It's possible that WUD mistook a merge/CI build for the release tag as an update and installed it automatically. Afterwards, the database was migrated to a state that current public releases no longer recognize.

storm sigil May 31, 2026, 9:37 AM

#

That sounds like something is seriously wrong in WUD then

thick pulsar May 31, 2026, 9:38 AM

#

It's possible, I'd also like to look at the WUD logs, but since my last SSD failed due to hardware issues, I no longer have access to the logs.

thick pulsar May 31, 2026, 10:41 AM

#

When my server installed version 3.0.0, it migrated my database accordingly, so the current release, version 2.7.5, could no longer use it. I then made a backup of the version 3.0.0 database; if it's useful to you, I can provide it.

#

it is around 60MB and has around 250000 lines

wet oak May 31, 2026, 10:51 AM

#

We don’t have a need for that

thick pulsar May 31, 2026, 10:51 AM

#

ok

#

is there anything else i can do, like removing the v3.0.0 image or smt?

wet oak May 31, 2026, 12:59 PM

#

Yes? I don’t really understand the question

#

You should be deleting the unsupported commit preview branch and back to a supported install like we linked above

broken kiln Jun 1, 2026, 4:45 PM

#

I think the TLDR is that using WUD without any configuration is not a good idea, especially with Immich. We publish development and test related docker builds to ghcr and WUD probably is upgrading to them.

#v3.0.0

References

Checklist

Information