What Changed in the ZimaOS 1.7.0 Update Workflow?
A community member reported that after moving from ZimaOS 1.6.2 to 1.7.0, containers using dynamic tags such as :latest no longer appeared to receive the same update notifications. The report specifically distinguishes registry image changes from App Store manifest version changes. This is a community-observed behavior, not a claim that every 1.7.0 installation behaves identically.
For current platform information, check the ZimaOS overview and the ZimaOS App Store hardware guide.
How Community Members Forced a Container Refresh
One workaround reported in the thread was opening the app's management screen and pressing Save without changing settings, which triggered an image check and re-pull. The original poster also mentioned manually pulling an image from the terminal. Before doing either, record the current image tag and persistent volume mappings so that an update does not become a configuration-loss event.
Why Image Tags and Store Versions Are Different
A Docker image tag is a registry reference, while an application catalog can maintain its own version metadata. Docker documents how image pulls resolve registry content in its image pull reference. LinuxServer also documents its container image conventions at LinuxServer container execution. This distinction explains why a catalog badge and the newest registry image do not necessarily represent the same signal.
What ZimaOS Said About the Feedback
An IceWhale staff reply on August 11, 2026 said the team planned significant improvements to update and installation mechanisms in the next App Store release. Treat that as a dated roadmap statement rather than a guarantee about the current build. For other app-management cases, the ZimaOS community showcase can provide additional context.
