Upgrading from v1.109 to latest
There are 25 pages of releases since my current version - any tips or guidance on the best strategy to upgrade?
Is the best approach to literally just upgrade release by release, using the IMMICH_VERSION flag in the .env? it's currently set to "release" in my file, but I guess I should set it to 1.12, and run docker compose? then 1.13 etc. etc.
14 Replies
:wave: Hey @FanBoy,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: 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.and yes I know my server is 1 year behind, but I went travelling 😉
Read the ones with breaking changes
Please make sure you have read and followed the release notes: https://github.com/immich-app/immich/discussions?discussions_q=label%3Achangelog%3Abreaking-change+sort%3Adate_created
(this link is filtered to that)
But it'll be quite an endeavour
Most importantly, take backups as you go (and before you start), and take your time
yep will do! Ah thank you, didn't know you could filter. Cheers 🙂
@bo0tzz does dockerhub maybe not retain images going that far back? I've set my IMMICH_VERSION=v1.11.0_17-dev and yet docker compose complains Error response from daemon: manifest unknown
although now I'm wondering about this -dev business, since -release is appended in the docker-compose.yml
You're saying you're coming from 1.109, no? Why do you want to jump to one of the very first versions three years ago then? 😅
Like, 1.109 >> 1.11
ah lol
yes
it's late 😄 I should do this in the morning hah
I just realised myself when I found dockerhub images goes back 2 years to 1.75
and was like hang on, 109 > 75 😄
Hahahahah
this is kind of fun though, I've missed a year of immich development, now I get to catch up release by release
Turns out, we've been doing a lot in the past year :P
no doubt!
I bought a lifetime key just before going on my travels, in anticipation of needing it on my returns
"needing"?
well, wanting 😛
ooooh folders in 113!
exciting hah
man, this is the second time the vector stuff has totally hosed my database, but thank goodness for gpt now, took 10 mins to fix
Can I remove the vector/vectors stuff now? Since vchord is working
root@lxc-postgresql:~# psql -U postgres -d immich -c "SELECT extname, extversion FROM pg_extension ORDER BY 1;"
extname | extversion
---------------+------------
amcheck | 1.3
cube | 1.5
earthdistance | 1.1
pg_trgm | 1.6
plpgsql | 1.0
unaccent | 1.1
uuid-ossp | 1.1
vchord | 0.5.1
vector | 0.8.1
vectors | 0.2.1
(10 rows)
ah nvm, found it in the notes now
Okay, so I had the wrong vchord. Got <4 running now.
root@lxc-postgresql:~# psql -U postgres -d immich -c "SELECT extname, extversion FROM pg_extension ORDER BY 1;"
extname | extversion
---------------+------------
amcheck | 1.3
cube | 1.5
earthdistance | 1.1
pg_trgm | 1.6
plpgsql | 1.0
unaccent | 1.1
uuid-ossp | 1.1
vchord | 0.3.0
vector | 0.8.1
vectors | 0.2.1
(10 rows)
But I still don't see anything in the server logs about Reindexing
ah well, I forced it with DB_VECTOR_EXTENSION=vectorchord