Practical answer: Zima Linux Client v2.0.0 is clearly built for ZimaOS. A contributor also reported that it can be used with CasaOS, but the project documentation does not list CasaOS as a formally supported target. Treat CasaOS compatibility as something to verify by function—device discovery, SMB access, app URLs, and remote networking—not as a blanket guarantee.
The original question was refreshingly simple: “Is this compatible with both CasaOS and ZimaOS?” The useful answer needs one extra layer: what does “compatible” mean for this client?
What v2.0.0 is actually designed to do
The Zima Linux Client project describes the application as a desktop client for ZimaOS with these core functions:
- discover ZimaOS devices on the local network;
- connect remotely through a Remote ID using ZeroTier;
- browse and mount SMB/CIFS shares;
- open Docker applications;
- run backup jobs from local folders to server shares.
That is the correct compatibility checklist. If those interfaces behave as expected on your server, the client can be useful. If a CasaOS installation does not expose something in the format the client expects, “it launches” is not enough to call the whole workflow compatible.
ZimaOS compatibility is the documented path
ZimaOS is the project's stated target throughout the README. The current Zima Client connectivity also describes ZimaOS as the server-side platform for remote files, dashboard access, Docker app entry, and mobile backup.
The Zima Client workflow is useful if you want the product-level explanation rather than the Linux community client's implementation details.
For CasaOS, verify the four functions instead of trusting one label
CasaOS and ZimaOS share enough self-hosting concepts that a client may work across both, especially around SMB and web apps. But the Linux client's README does not currently document CasaOS as its official target. Use this short test matrix:
| Function | What to test on CasaOS | Pass condition |
|---|---|---|
| Local discovery | Run “Scan Local Network” | Your server is discovered or can be reached manually. |
| SMB | Open a known CasaOS SMB share | The client can list and mount the share with correct credentials. |
| Docker apps | Open an installed web app | The app URL resolves and loads through the client. |
| Remote ID | Test remote connectivity from another network | The ZeroTier-backed path connects and the target services remain reachable. |
Passing one row does not prove the others. For example, SMB can work even if automatic device discovery does not.
Know what v2.0.0 supports on the Linux computer itself
The version 2.0.0 release is much more precise than the short compatibility answer. Version 2.0.0 is the first non-alpha release of the rewrite and provides packages for:
- Debian / Ubuntu / Zorin / Mint / Pop!_OS / PikaOS via
.deb; - Fedora / openSUSE / RHEL derivatives via
.rpm; - Arch / Manjaro via a pacman package;
- an AppImage for other compatible x86_64 systems.
The release is x86_64 only. It explicitly says arm64 is not covered. That matters because “CasaOS-compatible server” and “Linux desktop supported by this client” are two different compatibility questions.
Remote ID depends on ZeroTier, and the package format matters
The client bundles ZeroTier for its Remote-ID route. ZeroTier virtual networks connect devices as if they were on the same local network. That explains why the client can reach SMB shares and web apps without requiring them to be directly exposed to the public internet.
There is an important v2.0.0 detail: the release notes say the Remote-ID route needs CAP_NET_ADMIN on the bundled ZeroTier, and the normal package installer grants that capability. The AppImage does not perform the same installation step, so it is not equivalent if Remote ID is the feature you care about.
A better way to interpret “compatible with CasaOS”
Use three levels:
- Documented support: ZimaOS is explicitly named by the project.
- Reported compatibility: CasaOS was reported as working by the contributor in the real user Q&A.
- Your verified compatibility: the specific client version passes the discovery, SMB, Docker-app, and remote-access tests that matter to your setup.
This framing avoids both extremes: dismissing a real working CasaOS report, or turning one short confirmation into an official support promise the repository does not make.
If you want hardware that is officially positioned to run both ZimaOS and CasaOS, ZimaBoard 2 lists both in its compatible operating systems. That hardware compatibility is separate from the Linux client's own software support matrix.
FAQ
Does Zima Linux Client v2.0.0 support ZimaOS?
Yes. ZimaOS is the explicit target of the project and its documented discovery, SMB, Docker-app, backup, and Remote-ID workflows.
Does it officially support CasaOS?
The user Q&A reports that it works with CasaOS, but the project's README is written for ZimaOS and does not currently present CasaOS as a formal support target. Test the functions you need.
Can I install v2.0.0 on ARM Linux?
No supported arm64 build is listed for v2.0.0. The release notes state that the published packages are x86_64.
Why might the AppImage connect differently from the .deb or .rpm package?
The v2.0.0 release notes say the Remote-ID route needs a capability grant for bundled ZeroTier. The package installer can configure that; the AppImage does not perform the same installation step.
