Duplicacy
Container
Duplicacy backs up your files to many cloud storages with client-side encryption and the highest level of deduplication
Image details
Configuration
TypeContainermediadepot/duplicacy:latest3875/tcp/config : /opt/mediadepot/apps/duplicacy/config/logs : /opt/mediadepot/apps/duplicacy/logs/cache : /opt/mediadepot/apps/duplicacy/cache/source/apps : /opt/mediadepot/apps//source/storage : /media/storage/TZ=America/Los_Angelestraefik.enable=truetraefik.http.services.duplicacy.loadbalancer.server.port=3875traefik.http.routers.duplicacy.entrypoints=websecuretraefik.http.routers.duplicacy.tls.certresolver=mydnschallengeTemplate by mediadepot
Standalone Install
Select an install method, to see config/commands for deploying Duplicacy
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Duplicacy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation.
Duplicacy-Web wrapper
This is a wrapper around http://duplicacy.com web GUI.Two branches are supported:
latest: the classic one with the fixed version of duplicacyweb baked into the image. x8664 only.mini: The container downloads and caches the correct binary of duplicacyweb for the host architecture and selected version on start. To update/downgrade to another version change the environment variable and restart the container. Supports x86x64 and arm.
Notes:
- Arm detection is untested.
- Download-on-demand approach was already used by duplicacyweb to fetch the updated version of a duplicacy cli engine. The
minicontainer now extends this behavior to duplicacyweb itself making it easy to switch between versions at your cadence.
Volumes
/config -- is where configuration data will be stored. Should be backed up./logs -- logs will go there. /cache -- transient and temporary files will be stored here. Can be safely deleted.Environment variables
Common variables
USR_ID and GRP_ID: User and group ID under which the duplicacyweb will be running.TZ: time zone. Refer to https://en.wikipedia.org/wiki/ListoftzdatabasetimezonesUSR_ID and GRP_ID can be customized. Container will run as that user. By default user 0 (root) is used.:mini only
DUPLICACY_WEB_VERSION: Specifies version of duplicacyweb to fetch and use. To apply the changes restart the container. This makes the
:mini version behave more like a thin adapter layer as opposed to true self-encompassing container. To run
An example for:mini branch; the duplicacyweb version is selectable via environment variable:
``` bash
docker run --name duplicacy-web-docker-container \
--hostname duplicacy-web-docker-instance \
--publish 3875:3875/tcp \
--env USR_ID=$(id -u) \
--env GRP_ID=$(id -g) \
--env TZ="America/Los_Angeles" \
--env DUPLICACY_WEB_VERSION="1.4.1" \
--volume ~/Library/Duplicacy:/config \
--volume ~/Library/Logs/Duplicacy/:/logs \
--volume ~/Library/Caches/Duplicacy:/cache \
--volume ~:/backuproot:ro \
saspus/duplicacy-web:mini
An example for `:latest` branch; the duplicacy_web version is baked into the container:
``` bash
docker run --name duplicacy-web-docker-container \
--hostname duplicacy-web-docker-instance \
--publish 3875:3875/tcp \
--env USR_ID=$(id -u) \
--env GRP_ID=$(id -g) \
--env TZ="America/Los_Angeles" \
--volume ~/Library/Duplicacy:/config \
--volume ~/Library/Logs/Duplicacy/:/logs \
--volume ~/Library/Caches/Duplicacy:/cache \
--volume ~:/backuproot:ro \
saspus/duplicacy-web:latest Note, it's important to pass hostname, as duplicacy license is requested based on hostname and machine-id provided by dbus. Machine-id will be persisted in the /config directory.
To use
Go to http://hostname:3875Source
https://bitbucket.org/saspus/duplicacy-web-docker-containerServe Duplicacy on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying duplicacy.example.com to http://duplicacy:3875
Add this to your Caddyfile
duplicacy.example.com {
reverse_proxy http://duplicacy:3875
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs duplicacy - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Published on a random port
This template exposes 3875/tcp without setting a host port,
so Docker picks a random free one on every deploy.
- Find it in the Ports column of Portainer's container list, or with
docker port duplicacy
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /opt/mediadepot/apps/duplicacy/config(and the same for the other mapped folders)
Image won't pull
Test the pull directly on the host: docker pull mediadepot/duplicacy:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within duplicacy's repo
- Template not working: Open an issue on mediadepot/templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Duplicacy runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Duplicacy needs bundled into one download. This template pulls mediadepot/duplicacy:latest, which Docker fetches once (about 17 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Duplicacy's comes from Docker Hub, published by mediadepot.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:
3875, published on a random host port
Volumes
A volume is where Duplicacy keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/configfrom/opt/mediadepot/apps/duplicacy/configon the host/logsfrom/opt/mediadepot/apps/duplicacy/logson the host/cachefrom/opt/mediadepot/apps/duplicacy/cacheon the host/source/appsfrom/opt/mediadepot/apps/on the host/source/storagefrom/media/storage/on the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Duplicacy takes 1 of them, all with defaults you can leave alone or tweak:
TZ, defaults toAmerica/Los_Angeles
Networking
Nothing custom is set, so Duplicacy sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container duplicacy. That's what you'll spot in the containers list and use in commands like docker logs duplicacy.
Labels
Labels are small notes pinned to the container. They don't change how Duplicacy behaves, but other tools read them, most often a reverse proxy like Traefik working out which apps to route where. This template sets:
traefik.enable=truetraefik.http.services.duplicacy.loadbalancer.server.port=3875traefik.http.routers.duplicacy.entrypoints=websecuretraefik.http.routers.duplicacy.tls.certresolver=mydnschallenge
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Duplicacy up. Add the template list to Portainer once, then deploying Duplicacy is a click rather than a wall of config.