When ZimaOS repeatedly marks every Docker container as updateable even after an update, the badge does not by itself prove that new application code is available. The 2025 thread was tied to ZimaOS 1.5.2/1.5.3 and containers using the mutable latest tag.
A community reply attributed the behavior to image digest tracking. That explanation is plausible, but it was not an IceWhale engineering statement, so the safer current approach is to verify the actual image identity before repeatedly recreating containers.
Why latest Makes Update State Harder to Read
Docker tags are names that can be moved to a different image. The upstream Docker image pull guide explains that an image digest is an immutable identifier, while a tag can be pulled again to obtain a newer image.
That means :latest is not a version number. It can change without the application’s visible version label changing, and registries can rebuild an image while preserving the same software release string.
Verify Before Clicking Update Again
Check the container’s configured image tag, the locally stored image ID or digest, and the upstream release notes. If the digest and app release are already current, repeatedly clicking Update adds risk without giving you useful evidence.
If the app offers stable version tags, pinning a known release can make update behavior easier to reason about. Do not pin blindly when the project expects security fixes only through a rolling tag; read the app’s own release policy first.
Current ZimaOS Has Changed Since the Thread
The ZimaOS 1.7.1 notes say Docker startup, networking, web URLs, YAML compatibility and app migration were improved. They do not specifically state that the old “every app has an update” badge was fixed.
So if the symptom still exists on 1.7.1, capture one affected image name, tag, local digest and post-update digest before reporting it. That turns a vague badge issue into a reproducible comparison.
Prefer Intentional Container Updates
The Docker app basics is a useful refresher on how ZimaOS manages containers. The ZimaOS 1.7 App Store gives current UI context.
Bottom Line
The original report was real, but “update available” is not the same as “new application version.” With rolling tags, verify the image digest and upstream release first. If ZimaOS still flags an unchanged digest after updating on the current release, report that as a current UI/update-detection bug with the digest evidence attached.
