This thread is best read as a snapshot of ZimaOS in late 2025, not as a current feature list. The author reported real frustrations after moving from CasaOS: macOS client reconnect problems, app installs that appeared stuck, bridge-network breakage after installing a proxy app, poor Russian localization, a deliberately locked-down host OS, limited ZVM device passthrough, basic backup behavior, and a blank btop panel.
Some of those were bugs, some were architectural choices, and several have changed since. The original author personally confirmed that btop monitoring worked after updating to 1.5.2. Current ZimaOS 1.7.1 also has a newer App Store, versioned Backup workflows, broader storage/network fixes, and a much more mature app/AI catalog. The read-only appliance model, however, remains intentional.
The btop Monitoring Problem Was Source-Confirmed Fixed on 1.5.2
The author updated the thread to say system monitoring worked correctly after moving to ZimaOS 1.5.2. That makes this one of the clearest items: it was not a permanent product limitation.
Current ZimaOS documentation continues to include btop-based system monitoring, which originally entered the product in the 1.3.x line.
A Stuck App Install Can Be UI State, Docker State, or Registry Failure
The community reply claimed Docker sometimes finished while the UI missed the update. That is plausible, but it was not an IceWhale diagnosis in this thread. Modern App Store failures should be separated into:
- image pull/DNS/registry failure;
- container create/start failure;
- healthy container but stale dashboard state;
- application WebUI/network misconfiguration.
Do not normalize “reboot the NAS every time” as the permanent fix for a current installation.
V2RayA Breaking Bridge Apps Was Not Proven to Be a ZimaOS Core Bug
The source author said bridge-network applications stopped opening after installing V2RayA. A community reply suggested proxy/DNS changes could have disrupted Docker bridge name resolution. The thread contains no logs or IceWhale confirmation tying the failure to one exact DNS or routing rule.
When a proxy/VPN container changes routing, DNS, iptables/nftables, or Docker network namespaces, inspect those changes before blaming every affected app.
The Read-Only Host Is a Design Choice That Still Exists
The author disliked not being able to install arbitrary host packages. That criticism is valid for users who want a conventional Debian/Ubuntu server, but it is not an accidental bug. Current ZimaOS documentation still describes most system folders as read-only and expects applications to run through Docker, modules, VMs, or supported developer extensions.
Use the current ZimaOS CLI filesystem model when deciding whether the appliance approach fits your workflow.
ZVM Passthrough Was Limited, but the Situation Has Evolved
In late 2025, official replies elsewhere still described PCIe passthrough as a longer-term roadmap item. By 2026, community modules such as ZVM-Extra added USB/PCIe passthrough on top of libvirt, but that remains community software rather than proof that every passthrough workflow is now a built-in supported ZVM feature.
For critical GPU/HBA/USB passthrough, validate the current ZVM UI and IOMMU grouping instead of treating a 2025 complaint or a beta community module as the whole story.
The “Backup Just Copies Files” Complaint Is Now Historically Incomplete
Current ZimaOS Backup supports scheduled tasks, resumable/fault-tolerant transfers, local/USB/cloud/other-Zima destinations, and versioned restore points. It still is not the same product as an encrypted archive utility such as Duplicati.
Use the current ZimaOS Backup model before repeating the 2025 limitation.
The Reset UI Shows the Appliance Recovery Philosophy
The Durable Question Is Whether You Want an Appliance OS
Users who want unrestricted package management, hand-edited host services, and a conventional desktop/server distribution may still prefer Debian, Ubuntu, Proxmox, Unraid, or another platform. Users who want a managed NAS layer, Docker App Store, storage UI, remote access, and guarded system partitions may prefer ZimaOS.
The 2025 thread is valuable because it exposes that trade-off, but current evaluation should be done on ZimaOS 1.7.1 rather than assuming every 1.5-era symptom still exists.
ZimaOS Drawbacks FAQ
Was the broken btop panel fixed for the original user?
Yes. The author explicitly said monitoring worked after updating to ZimaOS 1.5.2.
Is the read-only host filesystem still intentional?
Yes. Current ZimaOS remains an appliance-style system where most host folders are read-only.
Is current Backup still only a one-time file copy?
No. Current Backup includes schedules, resumable transfers, multiple destination types, versions, and restore points.
