Community Solution

ZimaOS 1.7.0 Post-Update Issues: Memory Spikes, Folder Moves, App Restarts, and the 1.7.1 Fixes

A page-2 section of the July 2026 ZimaOS 1.7.0 release thread containing user reports about memory spikes, slow file copies, empty source folders after moves, apps needing manual restarts, reverse-proxy Web URL ports, and missing Internet Links. IceWhale recorded several issues; ZimaOS 1.7.1 later fixed abnormal memory use, empty folders after cut/move, and improved Docker startup and Web URL port handling.

ZimaOS 1.7.0 was a major App Store/UI release, but page 2 of the announcement quickly became a regression-report thread. Users liked App Store 2.0 and native YAML, while also reporting abnormal memory usage, slow file operations, empty source folders after moves, applications that needed manual restarts, reverse-proxy URL problems, and disappearing Internet Links.

The useful current way to read this thread is to separate reported symptoms from issues IceWhale acknowledged, then check what ZimaOS 1.7.1 actually fixed. Several page-2 reports map directly to 1.7.1 release notes, while others remain user feedback rather than confirmed product bugs.

One User Reported 90% Memory Usage and Very Slow External-Drive Copies

A 32 GB system reportedly climbed to around 90% memory usage after 1.7.0, while copying only a few gigabytes from an external drive took many hours. IceWhale asked for memory screenshots plus details about the drive connection, media type, and file count.

ZimaOS 1.7.1 later officially fixed abnormal memory usage in certain file operation scenarios, so this class of complaint received a concrete product-level fix.

Moving Folders Could Leave Empty Source Directories Behind

isanto1306 reported that files moved successfully between drives but the original source folder sometimes remained as an empty directory, especially when subfolders were involved. They said the behavior had started in 1.6.2 and remained in 1.7.0.

Dina explicitly recorded the issue and said it would be fixed. ZimaOS 1.7.1 later listed a fix for empty folders remaining after cutting folders in certain scenarios.

Some Apps Needed Manual Restart After the Upgrade

The same user said several containers failed to work immediately after upgrading and that four applications remained broken even after many manual restarts.

Dina asked for a diagnostic script plus app names and docker start results. This shows IceWhale was investigating restart-policy/container-start behavior rather than declaring one universal app failure.

ZimaOS 1.7.0 Plex container logs collected during post-update application startup troubleshooting
IceWhale asked affected users for real container logs and command-line start errors instead of treating every broken app tile as the same bug.

ZimaOS 1.7.1 Improved Docker Startup Efficiency

The 1.7.1 changelog does not say “all manual restart cases are fixed,” but it does list improved Docker container startup speed/efficiency and broader Docker network/YAML/Web URL improvements.

Use the ZimaOS 1.7.1 stability and Docker fixes before reproducing a 1.7.0 workaround.

Reverse-Proxy Web URLs Could Force the Internal Port into the Public URL

The page-2 report described a reverse-proxy domain that should have been https://mydomain.example but ZimaOS appended an internal port such as :8601. Dina recorded the issue and said it would be fixed.

ZimaOS 1.7.1 later improved Docker Web URL port configuration and URL handling for dynamic network environments, directly addressing this configuration area.

The user said dashboard Internet Links disappeared after the update even though applications and containers remained present. This had reportedly happened in an earlier beta too.

The public page-2 section does not show an IceWhale fix confirmation for that specific Web Links loss. Do not infer that 1.7.1 fixed it unless a later changelog explicitly says so.

One Heavy User Rolled Back to 1.6.2

After IceWhale requested diagnostics, the user said they had already rolled back to 1.6.2 because the NAS was used daily and 1.7.0 was not stable enough for their setup.

This is a user decision, not an official recommendation that everyone should downgrade from 1.7.0.

The Thread Also Contains a Community Manual RAUC Upgrade Method

Another user described copying the .raucb file under /DATA and running rauc install .... That was community guidance, not the main IceWhale upgrade path.

Current users should normally follow the supported update controls/release instructions and keep manual RAUC procedures for cases where they understand the dual-slot recovery model.

Current ZimaOS Is 1.7.1, Not the 1.7.0 Launch Build

IceWhale's current documentation identifies ZimaOS 1.7.1 as the latest stable release. When investigating one of these symptoms today, first confirm whether it reproduces on 1.7.1 before applying a rollback or manual restart routine from launch day.

ZimaOS 1.7.0 Regression FAQ

Did 1.7.1 fix abnormal memory usage during some file operations?

Yes. That is explicitly listed in the 1.7.1 changelog.

Did 1.7.1 fix empty source folders after cut/move?

Yes. The changelog explicitly lists that fix.

Did IceWhale confirm every app-restart problem was fixed?

No. 1.7.1 improved Docker startup, but the source investigation did not reduce every broken app to one root cause.