Dropbox-by-otherguy

Dropbox client which syncs a local path with your cloud.

  • Backup
  • Cloud
Dropbox client which syncs a local path with your cloud. This community Docker image runs the official Dropbox desktop client inside a container, letting homelab and Unraid users automatically back up and sync a mounted folder to their Dropbox account. Because the client does not support FUSE filesystems, you must point it at a direct disk path (for example /mnt/disk1/Dropbox) rather than /mnt/user.

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.

37/100 Low

Maintained
0last commit 1243 days ago
Popular
41112 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
701 GB minimum RAM
Security check
85no serious findings, CI

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

GitHub stars
112
Open issues
21
Last commit
2023-06-27
Latest release
1.12.0
License
MIT
Activity
stale

Checked 20 days ago - source: GitHub (otherguy/docker-dropbox)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

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

First-install notes

  • Connect Dropbox on first run Enter the Dropbox app key (the code that tells Dropbox which app is asking for access) and finish the sign-in/authorization flow. Without this connection, the app cannot talk to your Dropbox account or access your files. source
  • Grant only the access you need When asked what permissions to allow, choose only what the app actually needs, such as read-only account info. Broader permissions can let the app do more than you expect, and if authorization fails or is canceled, the app has no Dropbox connection to use. source
  • Store token details securely If you manually set up a short-lived token (a temporary login code), keep the access token, refresh token, and expiration date in secure storage. Without the refresh details, the app may not be able to renew the expired token and will stop working. source
  • Linking your account on first run After installing the container, open the container logs and wait until a Dropbox URL is printed, then open that URL in a browser and confirm to link the container with your Dropbox account. Syncing starts automatically once linked. source
  • Path requirements (FUSE not supported) The official Dropbox client does not support FUSE filesystems, so /mnt/user cannot be used. Use a direct disk path instead: /mnt/disk1/Dropbox (share cache set to No), /mnt/cache/Dropbox (cache set to Only), or /mnt/disk1/Dropbox with cache Yes (new files upload only after the Mover moves them). source

Fetched 37 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why can't I mount the Dropbox folder from macOS into the container?

The Dropbox client rejects unsupported filesystems, including the FUSE mount used for macOS Docker volumes. The earlier filesystem fix no longer bypasses newer Dropbox client detection, and old clients are rejected by Dropbox API servers.

Which directory mounts are needed for the container's settings and synced Dropbox data?

Mount the host settings folder to /opt/dropbox. Mount the host Dropbox data folder to /opt/dropbox/Dropbox.

How should I match file ownership inside the container?

Set DROPBOX_UID and DROPBOX_GID to the host user and group IDs. The quickstart example also sets TZ and POLLING_INTERVAL.

Does the quickstart require a published port?

The quickstart command uses host networking and includes no published port mapping. It is set up to run the Dropbox sync client with local folder mounts.

What can happen when I check the Dropbox version inside the container?

The version check can return incorrect information. It may say Dropbox daemon version: Not installed.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads