1.131 to 1.137 Update failed
I'm running immich on docker with portainer.
I failed to understand the breaking changes update requirements in the first place and jumped from 1.131 to 1.137.
So I did the following so far:
1. Update from 1.131 to 1.137 [fail from my side]
2. Downgrade to Version 1.131 [worked]
3. Update to Version 1.132.0 [worked]
4. Start the container [worked]
5. Modify Docker Compose [as far as I understood it's only the image link of the db which changed?]
6. Update to Version 1.137 [doesn't start any longer: /bin/bash: line 1: start.sh: command not found]
I tried downgrading to 1.132.0, but even that doesn't work any more.
I'm stuck and don't know know how to move on :/
61 Replies
:wave: Hey @plasma,
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. :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.docker-compose.yml + env file
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
So 1.133 has more breaking changes indeed. Did you see this?
No I didn't 😫
I'll change the compose file accordingly and report back!
Always read release notes thoroughly ;)
Especially breaking changes ones
Also note that this code block is scrollable
It seems that I already changed the image link, but didn't remove the clutter at the end.
I rebuild the container (with 1.137 - latest release), but it won't start. Should I try another older version first?
Please share the logs
Also, "clutter" is a funny word lmao
the container log repeats:
/bin/bash: line 1: start.sh: command not found
Could you share your current compose file?
docker-compose.yml
What did you do after changing your compose file?
I went into portainer and recreated the container (incl. re-pulling the latest image)
If you still get this it must not have actually recreated the container
How do I force it to use the compose file to recreate the container?
Idk about portainer
or can I somehow observe which compose file was used to create the current container?
With the cli it'd be
docker compose up -d --force-recreateI guess that I could ssh on the server and do that
I don't follow
You're changing the same stack in portainer, no?
I'm not sure tbh. I always focused on the single container (immich-server) to recreate it. Is that wrong?
Yes, you're changing the database
So you want to recreate the database container
Ok, so I need to recreate the whole stack? Please confirm.
Also I found in portainer, that the stack has a certain docker compose defined in the web-editor. This is not relevant I guess, as there's the base config from the tutorial from mariushosting, which I used.
And I just checked in the immich-redis container. It seems that the image link is wrong (which changed in the breaking change)
Also I found in portainer, that the stack has a certain docker compose defined in the web-editor. This is not relevant I guessWhat not relevant? That's the compose it's using no? Where are you changing the compose file? That doesn't matter
I'm not entirely sure which compose is used
A. The one in the web editor of the stack
B. The one in the filesystem docker/immich-app/docker-compose.yml
If you're using portainer you should edit the UI one
FWIW all of this aren't Immich problems. You should probably go learn portainer/docker a bit instead of just following a tutorial blindly without having any clue of what you're doing
here's the compose file from the UI
I'm absolutely with you! I tried to get some knowledge on this, but maybe I'm just too stupid. I tried google/chatgpt, but didn't get answers to my questions :/ Can you recommend a basic docker guide?
Right that has a bunch of mariushosting crap in there
but maybe I'm just too stupid.Don't say this. There's no such thing I don't know of good guides, I'd probably recommend youtube videos or just reading the docs + trying stuff out with basic compose files/containers
Should I swap the stuff out and replace by a up-to-date compose file?
Or start completely new (probably risking to lose my immich data)?
I'd recommend that (we even have a dedicated portainer guide https://immich.app/docs/install/portainer) but you cannot just straight up replace it if you want it to start working again as before
You could also start from scratch and do a backup + restore, yes
do I need to get the 'old' stack running to create a backup of my data? Or can I pull it from the 'old' folder structure without immich running?
You don't have current backups?
I simply auto-saved a backup of the whole immich folder. I just stumbled across https://immich.app/docs/administration/backup-and-restore and it recommends not doing it that way.
I see the automatical backup dumps of the db (e.g. immich-db-backup-1754265600012.sql.gz) in my files.
So when people say "x is not a backup tool" what they are actually saying is "you probably don't actually want a single point in time copy of your data", which is what that tool is doing.
And that "backup tools" exist today that:
- can run on a schedule
- only copy new/changed data (incremental)
keep track of changes over time in the backup, with the option to restore to a previous version
This gives you the ability to recover a file that was deleted some time ago, restore to a point prior to data corruption, etc., all while being space efficient (similar blocks are deduplicated)
Popular backup tools are restic and borg.
You should really have solid backups figured out before migrating from gphotos or similar to Immich. You're dealing with very important data here. Immich isn't a good project to get started with self-hosting
I agree. I have still a lot to learn and immich may be a stupid idea to start with.
you set the bar high so you can learn a lot, might not be a bad idea after all 😄
Still gotta make sure your data is safe though :D
The asset data is safe and backedup multiple times. But the db data only with the auto dumps 🙄
Ah if you have your actual assets backed up that definitely already helps 😅
I merged my config in a newer compose file and it didn't work. Not sure if it's worth the hustle to get this frankenstein-marius-hosting-monster to work. I'll start a new stack following the portainer instructions from immich.
Thank you @Daniel for helping me on this (even though it's not immich-releated)!
Feel free to keep us updated here :)
The new stack was created ✅ But now I have issues importing the backup.
The restore process only starts the postgres server (and the other ones later). How can I do this when I launch the whole immich stack in portainer?
https://immich.app/docs/administration/backup-and-restore#manual-backup-and-restore
Can I even import my old database (from the failed stack) into 1.137.x?
That could cause weirdness. I'd recommend importing into the same version and then upgrading
Or importing into 1.133 should probably be fine too
You just really need to make sure Immich hasn't started before
Only starting the DB is important
(I have no idea how to do that with portainer you need to google that yourself)
Does the database backup restore metadata? I was dumb and havent done a backup yet. I pulled all the assets from the directories on my NAS (TrueNAS) and have a db backup using the docker command from the Immich docs. So I have all the photos, they just all say they were created 2025, I'm assuming that meta data is in the database
did you just do a find on jpeg files or something?
Metadata is stored in xmp files along the photos, and in the database
I have most of the original photos (95%+), I did have a weird issue where some photos that were the correct date before, are now at the wrong date, not sure, but also not a huge deal, just a bit annoying
Nothing on those xmp files? 🙂
Imo I just took a 1h tutorial guide about Docker on YT and only tried using Docker commands since you can lunch everything with less than 5 commands using Docker Compose 🙂 Portainer has a great UI but I feel like I lose control.
Something like https://www.youtube.com/watch?v=eGz9DS-aIeY&t=59s&pp=ygUVZG9ja2VyIHR1dG9yaWFsIGd1aWRl or https://www.youtube.com/watch?v=pTFZFxd4hOI&pp=ygUVZG9ja2VyIHR1dG9yaWFsIGd1aWRl
had same problem deleteing some env fixed it
"some env" 👀
?
its always the env files when you upgrade, everytime
I haven't changed my env in a year
Lucky you
Upgrading immich is worse than a coin flip. when upgrading, but to help others when they search for this either delete all the env of course save them or just dele the ones that dont have db info everything else can go or be put back
I don't think this is correct 🤔 I've seen more issues with installation with custom setup, or running on other system like TrueNAS, unRaid...etc. If you are just running a linux server with Docker, upgrade should be very smooth
I've been upgrading from version 0.0.0 and I ran into an issue once when one of the migration take up more OS disk space available
@Goose do you read the release notes before you upgrade?
Deleting your env is the weirdest thing to do tbh
If you were talking about changing out compose then that would maybe make sense
I only suffered / sweat when passing to 1.131 to 1.137 but the notes on github were pretty useful and verything went well luckily 🙂
but yh, I agree that with Docker is ez pz