Even though I use the latest version when I launch a docker container, when the system detects that a new version is available, it installs the stable version instead of the latest one.
It seems that it is a problem of Zimaos.
I also have the same problem, and i canât find a solution for that. Is that any way of manually instaling the lattest versions?
Cautious!
The current design is for stability that the version number is fixed after you update to one version one day. Even if it is tagged with latest
, the version number is fixed. The latest
is effective only at the time you do the installation.
Cautious! Cautious! You can do this to upgrade. But there are possibilities that you break the app.
Try to open the settings panel of the app and click the save button without modifying the parameters. It will trigger upgrading/re-installing again!
We might modify the design of the tag field. Look forward to your response.
So does that mean that the latest tag is essentially useless after that first install? Itâs a lot harder to keep up to date with containers if I have to manually type in the latest version number instead of just restarting my containers that have the âlatestâ tag.
Yes, like I said, you could trigger an update by clicking the save button. But it has some risk.
Is that still the case? Youâve crossed it out and Iâve had to manually update custom containers currently using version numbers instead of just the latest tag like I used to already. (Radarr for instance just now says it has an update. I save the current container that has the latest tag and it doesnât update the container)
@LinkLeong Could you take a look at this?
I had similar issues with Immich. I kept getting a notification of an update for Immich but each time it tried to run the update, it would revert back to the current version. I checked the GitHub for the updated version number and then added this in the âSettings/Tagâ field and it has now updated Immich to version v1.132.3.
I donât know if this should be marked as the solution to the problem truthfully. It hasnât solved the issue of the latest tag not working, itâs just them stating that theyâre having to manually update the containers themselves now with the version numbers
I have remove the solution mark. Thanks for your feedback.
Itâs worth mentioning that itâs not just the âlatestâ tag that has this issue, the âdevelopâ tag has the same one. Basically the container doesnât actually look at the main repository and update to the most recent version with any named tags anymore. I imagine âstableâ tags will have the same issue.
Thanks for your info. For now, if you want to upgrade to a specific version, manually edit the version number in the settings panel of the app. Remember to click the save button to trigger the upgrade.