docker resilio sync
3.0.0.1409-1-ls194
The LinuxServer.io team brings you another container release featuring:
Find us at:
Resilio-sync (formerly BitTorrent Sync) uses the BitTorrent protocol to sync files and folders between all of your devices. There are both free and paid versions, this container supports both. There is an official sync image but we created this one as it supports user mapping to simplify permissions for volumes.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/resilio-sync:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ✅ | arm64v8-<version tag> |
| armhf |
<your-ip>:8888, for account creation and configuration.To help you get started creating a container from this image you can either use docker-compose or the docker cli.
---
services:
resilio-sync:
image: lscr.io/linuxserver/resilio-sync:latest
container_name: resilio-sync
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /path/to/resilio-sync/config:/config
- /path/to/downloads:/downloads
- /path/to/data:/sync
ports:
- 8888:8888
- 55555:55555
restart: unless-stoppeddocker run -d
--name=resilio-sync
-e PUID=1000
-e PGID=1000
-e TZ=Etc/UTC
-p 8888:8888
-p 55555:55555
-v /path/to/resilio-sync/config:/config
-v /path/to/downloads:/downloads
-v /path/to/data:/sync
--restart unless-stopped
lscr.io/linuxserver/resilio-sync:latestContainers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 8888 |
WebUI |
-p 55555 |
Sync Port. |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=Etc/UTC |
specify a timezone to use, see this list. |
-v /config |
Where resilio-sync should store its config file. |
-v /downloads |
Folder for downloads/cache. |
-v /sync |
Sync folders root. |
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariableWill set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:
id your_userExample output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Shell access whilst the container is running:
docker exec -it resilio-sync /bin/bashTo monitor the logs of the container in realtime:
docker logs -f resilio-syncContainer version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' resilio-syncImage version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/resilio-sync:latestMost of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Update images:
All images:
docker-compose pullSingle image:
docker-compose pull resilio-syncUpdate containers:
All containers:
docker-compose up -dSingle container:
docker-compose up -d resilio-syncYou can also remove the old dangling images:
docker image pruneUpdate the image:
docker pull lscr.io/linuxserver/resilio-sync:latestStop the running container:
docker stop resilio-syncDelete the container:
docker rm resilio-syncRecreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:
docker image pruneTip
We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-resilio-sync.git
cd docker-resilio-sync
docker build
--no-cache
--pull
-t lscr.io/linuxserver/resilio-sync:latest .The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
docker run --rm --privileged lscr.io/linuxserver/qemu-static --resetOnce registered you can define the dockerfile to use with -f Dockerfile.aarch64.
UMASK_SET in favor of UMASK in baseimage, see above for more information.
