I still cannot solve the problem, CasaOS says “Unable to update at the moment!” (in the devtool > Network the response is status 500 and {“message”:“compose app not match”}).
I suppose that CasaOS downloads the wrong compose (without the “v” in the image tag) and for some reason is stuck with the error… I tried restarting, didn’t works.
There’s a less risky way than “unstalling & reinstalling” stuff? Maybe update manually the wrong info that CasaOS uses or something.
Did you change the compose file? If you decide to remove the app just don’t delete the app data. I have not heard of other people not being able to update immich since this issue normally fixes itself.
Did you change the compose file?
What do you mean? Edit it from “Settings” in the Immich card? What should I edit exactly?
Is this secure? I mean update this manually, the next updates will be handled correctly by CasaOS?
Thank you in advance!
Looking to revive this thread as I am having the same issue and would like to know how to proceed.
Having the same issue, can’t update Immich, tried deleting it and re-installing but still on the same version. Please update repo.
After updating CasaOS to the newest version, this Fixed the issue of Immich not updating itself.
I was able to resolve this via some help I got from the immich Discord.
This process is what you can do each time you need to update your CasaOS instance of immich. From what I understand, we can’t rely on the built in update feature in CasaOS.
-Be aware of any breaking changes that have been found for the latest update. You can see that info here: immich-app/immich · Discussions · GitHub For me this meant I needed to make sure to update the immich-server Container port in Settings because that got broken in some update between the one I had and the one I was updating to.
-Updating generally means you’ll need to manually change some of the info in the Docker compose file. In this case you can do that via Settings (hover over immich in the CasaOS UI and click the 3 dot menu and click Settings.)
For the current version, as of 12/12/2024 (v1.122.2), the images below show what I changed to update mine:
This is what goes in the Tag field on the database tab: pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
After saving those changes my instance updated to 1.122.2 and I was all set.
How do you find this same information for future updates? You’ll need to compare the docker compose file from the update with the compose file(AKA what is in Settings) you are currently running.
To do that, go here: Releases · immich-app/immich · GitHub
Find the docker-compose.yml for the update. It should be listed under “Assets.”
You can go through that file manually and see what has changed
or
You can compare (do a diff) the new file with the one you are currently running
To get your current compose file, go into Settings for immich in Casa and export the compose file. The icon to do that is in the top bar of the Settings window. Looks like a square with an arrow coming out of it.
Doing that export will save a .yml file to your machine.
Now you can compare the .yml file from the github releases page with the one you just exported.
Google how to do a diff. There are free tools you can use. Like VSCode.
Doing the diff will show you what needs to change. Make those changes in Settings and Save. If everything went well, immich will update and you’ll be good.
I just learned this myself. Credit goes to Mraedis in the immich Discord.
Hope that helps.
This is a known issue. It’s not a BigBearCasaOS issue because the store gets updated. Normally you need to restart CasaOS, then it pulls in the changes.
You shouldn’t need to update manually because the Docker compose gets updated from BigBearCasaOS. When it doesn’t update, you normally have to restart CasaOS then it brings the update in.
You also can make sure the time is set correctly: How to Automatically Update Date, Time, and Timezone on Your Linux System
I went ahead and update the sha:
Either I didn’t try to restart CasaOS or it didn’t work. Either way, the manual update I wrote up above worked for me. This at least gives folks another thing to try if they’re having trouble getting this update done.
I see what’s wrong. You edited the main Docker compose, or you manually installed it instead of going through BigBearCasaOS. If this was being updated from BigBearCasaOS, then you should have a check then update like this:
If you continue with this setup, then you will not get updates from BigBearCasaOS.
Prior to going through the steps in my post I tried uninstalling immich and reinstalling (from the BigBear app store,) I tried the check and update path from the context menu on the icon and neither worked. The only thing I didn’t try in there was restarting CasaOS.
It’s good to know that I broke my ability to update via BigBear, but it seemed broken before so it isn’t a big loss to me unless there’s some problem with that.
Following this tutorial and after inspecting the docker-compose.yml file it uses ${IMMICH_VERSION:-release} and after downloading the file example.env, you can find that IMMICH_VERSION=release, before this I tried using latest as a tag in CasaOS and it didn’t work but it worked for other apps, but based on this I tried to use release tag and it works, Immich without machine learning finally updated for me using this tag, so, it uses release tag instead of latest, and hopefully this’ll work in future as well, I’ll test it out when an update comes, and I’ll test Check for Update from CasaOS, thanks for the info btw.
