Sync app goodsync style

Insight & Feedback
1

Hi everyone

I was wondering if it is for the specialists to develop an app similar to goodsync. Why?
Because i have the need to sync files from and to various cloud services like gdrive, Dropbox, onedrive, box and mega.nz, all this simoultaniously and from multiple accounts in each service.
The only way that i got it was through a vm in zvm. A vm with Ubuntu installed.
It would be nice be able to do it more natively, it would consume less hardware resources.
I leave the ideal for your analysis.

Thanks

1 Like
2

I believe this is a very valid request and a common real-world need.

I suggest keeping expectations realistic though: a GoodSync-level app is a large, commercial-grade sync engine (multi-cloud APIs, conflict handling, versioning, multi-account auth). That’s not a small or quick feature to build natively.

I believe the most practical solution today is rclone running directly on ZimaOS (CLI or container).
I suggest this over a full Ubuntu VM because it:

  • Supports all major clouds (GDrive, Dropbox, OneDrive, Box, Mega)
  • Handles multiple accounts
  • Uses far fewer CPU/RAM resources

I believe a native ZimaOS sync app would be excellent long-term, but I suggest rclone as the current lightweight, efficient path until IceWhale invests in a full sync framework.

3

Thanks for the support.
I tryed to install rclone, but no luck. I’m new in docker style Apps.
Is there any tutorial easy to understand?

4

I believe this tool is very powerful, but it is not beginner-safe by default.

I suggest treating rclone as an advanced utility, not a normal “sync app” like GoodSync. With one wrong option (for example Sync vs Copy, or the wrong direction), it can delete data very quickly.

For new users, I suggest:

  • Start with Copy (one-way) only
  • Never use “Sync” until you fully understand direction and deletions
  • Test with an empty test folder first
  • Do not mount or point rclone at system paths (/, /DATA, AppData, etc.)

I believe rclone works best when:

  • Used deliberately, not “set and forget”
  • Configured slowly, one cloud at a time

Until there’s a guided ZimaOS sync app with proper safeguards, I suggest rclone remains a power-user solution, even with the Web UI.

Simple & safe rclone install on ZimaOS (Docker)

This is the cleanest and least risky way to run rclone on ZimaOS.

:one: Create folders (one time)

mkdir -p /DATA/AppData/rclone/config
mkdir -p /DATA/AppData/rclone/data

:two: Run rclone with Web UI (no login, LAN only)

docker run -d \
  --name rclone \
  --restart unless-stopped \
  -p 5572:5572 \
  -v /DATA/AppData/rclone/config:/config \
  -v /DATA/AppData/rclone/data:/data \
  rclone/rclone \
  rcd --rc-web-gui --rc-addr :5572 --rc-no-auth --config /config/rclone.conf

:three: Open the Web UI

http://ZIMA_IP:5572

From here:

  • Add one cloud account
  • Use Copy (one-way) only
  • Test with a dummy folder inside /data

I believe this approach avoids heavy VMs, saves resources, and is the safest way to experiment, as long as users understand that rclone is powerful and unforgiving if misused.

If IceWhale ever ships a guided sync app with guardrails, this would be a great candidate, but for now, caution is key.

image
image2206Ă—1180 166 KB

1 Like
5

Thank you for your help and explanation.
I will test this isntrutions like you sugested.

Thanks again.

6

I tried to follow your instructions, but on the docker cli I got this error.

$ docker run -d \
>   --name rclone \
>   --restart unless-stopped \
>   -p 5572:5572 \
>   -v /DATA/AppData/rclone/config:/config \
>   -v /media/archivestorage/rclone:/data \
>   rclone/rclone \
>   rcd --rc-web-gui --rc-addr :5572 --rc-no-auth --config /config/rclone.conf
WARNING: Error loading config file: open /DATA/.docker/config.json: permission denied
docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Head "http://%2Fvar%2Frun%2Fdocker.sock/_ping": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.

I aslo tried it via gui + install a customized app It installed, and I have the icon but it won’t start.

I’ll need to give those directories perms for it once I figure out how.

I found this in the container log

{"log":"2026/01/01 18:09:22 NOTICE: Fatal error: unknown command \"rcd --rc-web-gui --rc-addr :5572 --rc-no-auth --config /config/rclone.conf\"
7

There are two separate issues here:

1: Docker permission error (this is the real blocker)

permission denied while trying to connect to the Docker daemon socket
/var/run/docker.sock

This means the command is not being run with sufficient privileges.

On ZimaOS:

  • Docker commands must be run as root or
  • Executed via the ZimaOS App / Custom App UI

Running docker run from a restricted shell or user will fail exactly like this.
This is not a rclone issue.

2: Invalid command format inside the container

Fatal error: unknown command "rcd --rc-web-gui --rc-addr :5572 --rc-no-auth --config /config/rclone.conf"

This happens when the entire command is passed as one string instead of arguments.

This usually occurs when:

  • Using GUI / Custom App fields incorrectly
  • Putting the whole command in a single “Command” box

The container expects:

rcd
--rc-web-gui
--rc-addr :5572
--rc-no-auth
--config /config/rclone.conf

as separate arguments, not one line.

Important clarification (to save pain)

I believe this highlights the bigger issue:

  • rclone looks simple, but is not beginner-safe
  • ZimaOS permissions + Docker + rclone flags = sharp edges
  • The Web UI does not make it consumer-friendly

This is exactly why many users hit a wall here.

Practical advice

I suggest one of the following:

  • Run rclone only via the ZimaOS App UI, with arguments split correctly
    or
  • Avoid rclone entirely unless you’re comfortable with Docker + CLI
    or
  • Use higher-level tools (Nextcloud clients, desktop sync, VM-based tools)

For many users, rclone is simply not worth the friction.

8

Itried it with the ZimaOS App UI and did the Docker CLI tab and pasted your step 2

image
image704Ă—230 16.4 KB

in it and that didn’t parse it right apparently. With that info I’ll take a look and try again via gui and a docker compose properly setup instead. If i can get that to work, I’ll post my compose here.

9

The command itself is fine, it runs correctly when executed directly from a proper root shell. The issue seems to be how the ZimaOS App UI / Docker CLI tab parses commands. In that context, the rcd --rc-web-gui … portion can end up being treated as a single argument, which is what triggers the “unknown command” behaviour.

So this isn’t really a rclone syntax problem, it’s more about how the UI passes arguments into Docker.

Moving to Docker Compose is a good approach here, it avoids parsing ambiguity, keeps the arguments explicit, and is generally easier for others to reproduce. If you get a working compose setup, sharing it would definitely be helpful for anyone following along.

10

Just to add some context from my side in case it helps others:

I spent a fair bit of time trying to get Google Drive working via rclone / Nextcloud, and ultimately gave up, not because it’s impossible, but because the experience is too inconsistent and fragile.

Between:

  • Google auth flows changing
  • Web-based auth not working cleanly inside containers
  • Ports already in use / redirect issues
  • ZimaOS UI vs CLI behaving differently
  • Commands working in one context and failing in another

It became very difficult to tell whether a failure was due to Google, rclone, Docker, or the execution environment.

None of this is obvious upfront, and for something that’s meant to be a “simple cloud sync,” the amount of moving parts makes it very easy to waste a lot of time with no guaranteed outcome.

In the end, I decided it wasn’t worth the complexity or risk. For now, I’m sticking with simpler, more predictable workflows and treating Google Drive as something to migrate away from rather than integrate tightly.

Hopefully this saves someone else a bit of frustration.

1 Like
11

Thanks for sharing your use case.
If the built-in backup app in ZimaOS were able to support more cloud services and provide synchronization (not just one-way backup), would that be close to your ideal solution?

We’d be very interested to know if this would meet your needs, or if there are any specific sync behaviors you’d consider essential.

image
image2048Ă—1374 136 KB

12

Hi
Yes, that could be a more complete solution, nevertheless it would be missing the multiple account in the same service,for example.
But with no doubt that would be a huge step towards the perfetion.
I appreciate your effort in this matter.
Thank you.

1 Like
13

Understand. Thanks!

14

Hi, any idea when backup app will add those feature ?
Or when Build Multiple Clones using rsync | Zimaspace Docs will be released ?
Thanks

1 Like
15

Thanks for your feedback! Quick update on the features you care about:

  1. Sync function is scheduled to launch with in 3 months.

  2. More cloud drive integrations and performance tweaks are in our roadmap, with the initial technical plan finalized.

As a small team, we need a bit more time to polish everything. Really appreciate your understanding!

1 Like
16

Hi

Those are great news. Looking foward for the updates.

I appreciate your effort. Thank you.

1 Like