Rsync Server

A lightweight, Alpine-based rsync server for synchronising and backing up files over SSH, suitable for scheduled transfers between an Unraid host and remote…

  • Backup
  • Cloud
  • Tools & Utilities
A lightweight, Alpine-based rsync server for synchronising and backing up files over SSH, suitable for scheduled transfers between an Unraid host and remote machines.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

55/100 Fair

Maintained
68last commit 78 days ago
Popular
3450 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
75no serious findings

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 53 days ago

GitHub stars
50
Open issues
7
Last commit
2026-09-04
Latest release
3.1
Activity
stale

Checked 21 days ago - source: GitHub (eea/eea.docker.rsync)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • SSH key setup Before starting the container, add your client's SSH public key to the SSH_AUTH_KEY_1 variable. To generate a key on your client: run 'ssh-keygen -t rsa -b 4096', press Enter three times to accept defaults, then display the key with 'cat ~/.ssh/id_rsa.pub'. Paste the full 'ssh-rsa AAA…' line into SSH_AUTH_KEY_1. Test the connection with: rsync --dry-run --itemize-changes --archive -e 'ssh -p 5533' source

Fetched 37 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I allow a client to connect to the rsync server?

Add the client's public SSH key to the SSH_AUTH_KEY_1 environment variable when starting the server. Additional client keys can be added with SSH_AUTH_KEY_n variables.

Which port should the Docker server expose for SSH-based rsync?

The documented Docker example maps host port 2222 to container port 22. The client rsync command then uses ssh -p 2222.

Do I need to persist SSH keys when recreating the containers?

Yes, persist the client key directory /root/.ssh and the server host key directory /ssh_host_keys in Docker volumes. The keys are created on first start and reused on later starts.

What volume do I mount for the rsync data?

Mount the data directory to /data in the container. The examples use server_vol_to_sync for the server and client_vol_to_sync for the client.

Can I run the rsync transfer automatically?

Set CRON_TASK_1 or CRON_TASK_2 on the client container to a cron command. The example runs an rsync command over SSH at a scheduled time.

Answers sourced from github.com

Community

Collected 47 days ago - public community threads