The original request was broader than “connect Google Drive.” The user wanted multiple accounts across Google Drive, Dropbox, OneDrive, Box, and MEGA, with two-way-style sync/transfer behavior, but without dedicating an Ubuntu VM to a commercial GoodSync client.
ZimaOS has moved significantly toward that use case. Current Files can connect Google Drive, Dropbox, and OneDrive directly, supports multiple accounts from the same provider, and lets users copy/move data between cloud and local storage. Current Backup can also use cloud, LAN, USB, or Zima sources/destinations with schedules and versions. That still is not identical to every GoodSync feature—especially arbitrary provider coverage, conflict rules, and true bidirectional synchronization semantics.
Current Files Supports Multiple Accounts from the Same Cloud Provider
IceWhale's current Cloud Drives documentation explicitly says users can connect two Google Drives or two OneDrives side by side. Connected cloud folders appear next to local storage in Files.
See the current multi-account Cloud Drives workflow.
Backup and Sync Are Not the Same Operation
Current IceWhale Backup documentation explicitly warns that cloud sync mirrors changes—including deletions—while Backup writes forward and keeps versions/restore points. Use Backup when protection is the goal; use copy/move/sync only when you understand the deletion semantics.
Use the current versioned Backup model.
rclone Remains a Powerful Multi-Provider Option
The community suggested rclone because it supports many cloud providers and multiple remotes/accounts with far less overhead than a full Ubuntu VM.
The same replies repeatedly warned that rclone sync can delete destination files to make two sides match. New users were advised to start with one-way copy against disposable test data.
One User Hit Docker Socket Permission Before rclone Even Started
SirWill's CLI attempt failed because the current shell user could not connect to /var/run/docker.sock. That was a Docker privilege issue, not evidence that rclone itself was broken.
The Custom App UI Also Passed the rclone Command Incorrectly
rcd ... command as one argument rather than separate arguments.The community concluded that a proper Docker Compose definition is clearer because each argument is explicit and reproducible.
IceWhale Did Engage with the Feature Request
777-Spider asked whether extending the built-in Backup app to more cloud services plus synchronization would meet the need. In January 2026, he said a sync function was scheduled within roughly three months and additional cloud integrations were on the roadmap.
That statement is historical roadmap evidence, not a guarantee that every proposed GoodSync capability has shipped. Evaluate the current Files/Backup feature set directly.
A Safe Current Choice Depends on the Job
- Browse/copy/move among Google Drive, Dropbox, OneDrive and local storage: use current Files.
- Versioned scheduled protection: use Backup.
- Unsupported providers or complex transfers: consider rclone with tested remotes and conservative commands.
- Commercial-grade bidirectional sync/conflict policies: verify whether your required behavior exists before replacing GoodSync.
Current Built-In Cloud Support Does Not Cover Every Provider from the Request
The original wish list included Google Drive, Dropbox, OneDrive, Box, and MEGA. Current IceWhale Cloud Drives documentation explicitly covers Google Drive, Dropbox, and OneDrive. Do not imply that Box and MEGA have the same built-in integration unless the current UI/docs add them.
That remaining provider gap is one reason rclone or another external sync engine can still matter.
Do Not Expose an rclone Web UI Started with --rc-no-auth
The community Docker example deliberately used --rc-no-auth and labeled it “LAN only.” That removes authentication from rclone's remote-control/Web UI endpoint. Anyone who can reach the port may gain powerful file-transfer control.
Keep it on a trusted network or configure authentication and a protected access path before remote use.
Cloud OAuth Is Part of the Operational Complexity
The thread also records Google authentication/redirect problems and differences between CLI and containerized browser flows. When a cloud connection fails, separate provider OAuth/redirect issues from Docker permissions, rclone command syntax, and ZimaOS storage mappings.
Test Deletion Semantics with Disposable Data
A GoodSync-style workflow is valuable because it makes direction and conflict behavior explicit. Before scheduling any rclone sync or other mirror operation, create two disposable folders, add/delete files on both sides, and verify exactly which side wins.
Multi-Cloud Sync FAQ
Can current ZimaOS connect multiple accounts from one provider?
Yes. Current Cloud Drives documentation explicitly supports multiple accounts from the same service.
Is Backup the same as bidirectional sync?
No. Current IceWhale documentation explicitly distinguishes backup/versioning from sync/mirroring.
Is rclone beginner-safe by default?
No. The source community repeatedly warns that direction and delete semantics must be tested carefully.
