#How do I upgrade to v3 in Custom App YAML environment

26 messages · Page 1 of 1 (latest)

fast grotto
#

Hi, I am fairly new to this whole topic but I was able to set up Immich on my Home NAS running with TrueNAS. When is was setting up, I was not able to find Immich as "original" App in the TrueNAS "app store", therefore I have set zp Immich as a "Custom App" via YAML File. The "disadvantage": it's not a typical docker environment, no docker commands, and there is no envelope file. Therefore I set all the envelope settings directly in the YAML file, like PostgresPW, Data Directory and so on.
But now I am unable to upgrade to version 3, because, as I said, I don't have an envelope file where I could set the version to "v3", but the YAML file refers to the "${IMMICH_VERSION:-RELEASE} version of Immich, and I can't set it directly to "v3" nor "v3.0.0" - I CAN. But if I do the app won't compose.
I wasn't able to find stable GHCR packages for immich_server and immich_machine_learning for v3 either. So I could not set them directly aswell.

Any advice?

scarlet bisonBOT
#

:wave: Hey @fast grotto,

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

#

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.

scarlet bisonBOT
severe swift
#

v3 isn't out yet @fast grotto

fast grotto
#

Thank you @severe swift , but then the newest blog post is irritating... The blog post has the tag "release" and talks about "we are thrilled to announce the next major version of Immich". And they tell, to edit the envelope file from v2 to v3. There is even a migration guide. This post is from 1st of July 2026.

pr-558.dev.immich.app/blog/v3.0.0-release

severe swift
#

Why are you reading the dev blog release notes

fast grotto
#

Because thats what I found after searching for "immich version 3"...

severe swift
#

Well if the URL didn't give it away yet, the images aren't out yet

#

It'll probably be out today, but you'll see the announcement and the blog on the actual blog URL 🙂

fast grotto
#

Okay. I am sorry for having bothered you. I thought it's the official blog because the internet search gave it to me. Anyway, now I know where the problem was. But IF the official release is out then, how do I get it then - will setting the version manually to v.3.0.0 directly in the YAML work?

severe swift
#

It's still compose, yes? Then that should work.

fast grotto
#

Thank you I will wait and then try

azure fossil
#

@fast grotto what search engine do you use?

fast grotto
#

In this case I used Google and DuckDuckGo.

#

It's actually the first entry when I search "immich version 3" - directly to the apparently Dev Blog.

#

@azure fossil so did I do something wrong?

azure fossil
#

No, DDG did

severe swift
#

bad DDG, bad

#

Brave also lists it FYI @azure fossil

azure fossil
#

Yeah so does kagi, either it's a shared index that's misbehaving or it actually is broken on our end

#

What confuses me is that it doesn't seem to be in google

#

which I would expect if it was our fault

fast grotto
#

@azure fossil my bad. It was only DuckDuckGo engine. Not Google.

#

... And it to be expected, that v3 launches somewhe this day? Because now I finally broke my immich_server. Server is at v3 and apps obviously at v2.7.5 - so they don't wanna sync anymore. And before a migrate bat to v2.7.5 on my server with a Postgres Dump, I might just wait for the final v3 release.

fast grotto
#

Nvm I was able to reroll to 2.7.5 and migrate the old Postgres back in.

fast grotto
#

And since 3.0 is released now, it worked with manually setting the version to 3.0.0 in the yaml file. This ticket is resloved.