I wanted to provide some feedback regarding the new UI and App Store mechanism introduced in ZimaOS 1.7.0.
While I appreciate the ongoing improvements to ZimaOS, the new update mechanism feels like a major step back compared to ZimaOS 1.6.2 when it comes to managing container updates.
The Issue:
In ZimaOS 1.6.2, the system properly checked Docker registries to see if an image’s digest had changed for containers using tags like :latest (e.g., lscr.io/linuxserver/plex:latest). If a new build was pushed upstream, ZimaOS would notify the user with an update button.
In ZimaOS 1.7.0, this behavior seems to have been replaced by strictly checking the version number in the ZimaOS App Store manifests.
As a result:
No Update Notifications: For popular containers that frequently push updates under the :latest tag (like Plex, LinuxServer.io containers, Arr-stack, Home Assistant, etc.), ZimaOS no longer shows any update badge/button because the store manifest version remains static.
Forced Workarounds: The only way to force an update currently is to open the app settings and hit Save without changing anything (which forces a re-pull), or to manually run docker pull via SSH/Terminal.
Relying on Third-Party Tools: Users now have to deploy third-party solutions like Watchtower via Custom App Compose files just to get basic update automation or notifications back.
Feature Request / Solution:
Could you please restore or add a direct Docker registry check for running containers, or at least provide a “Force Pull / Update” button in the app’s action menu (the 3 dots ⋮) for containers using image tags?
Relying solely on App Store manifests breaks the update flow for anyone running dynamic or custom Docker images.
Thanks for your hard work, and I hope this feedback helps improve the app management experience in upcoming patch releases!
This is not completely true. I have a custom installed app, When I hear from the developer of a new beta version to test, I click the app to go to manage , click save, it goes out to check the image, and installs the update. And that is minutes after the release sometimes.
So, no I never get a notice of an app update available for that app, but when I know there is one, it is easy to get it to update.
Solid, well-articulated feedback. The shift from digest-checking to manifest-version-checking really does break the whole :latest workflow, which is exactly how most self-hosters run LinuxServer and Arr containers. Having to hit Save to force a re-pull or bolt on Watchtower is a clear regression. A simple Force Pull button in the three-dot menu would fix most of this. Hope the devs pick this up, it’s a reasonable ask.
I agree with this. THe updates were always hard (I’m not super tech-savvy so not sure how to update through terminal commands). It would be great if there was a better option for updating both App Store versions (those are too outdated and not sure how can I update those) and custom installs (which is in my case mainly because the app store versions are outdated)
Thank you for your feedback; we will be making significant improvements to the update and installation mechanisms in the next App Store release. We fully understand your needs.