​​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​​

​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.

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling ghcr.io/linuxserver/resilio-sync 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:

Application Setup

• Webui is at <your-ip>:8888, for account creation and configuration.

• More info on setup at Resilio Sync​

Usage

Here are some example snippets to help you get started creating a container from this image.

docker-compose (recommended)

Compatible with docker-compose v2 schemas.

---
version: "2.1"
services:
  resilio-sync:
    image: ghcr.io/linuxserver/resilio-sync
    container_name: resilio-sync
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /path/to/config:/config
      - /path/to/downloads:/downloads
      - /path/to/data:/sync
    ports:
      - 8888:8888
      - 55555:55555
    restart: unless-stopped

docker cli

docker run -d \
  --name=resilio-sync \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 8888:8888 \
  -p 55555:55555 \
  -v /path/to/config:/config \
  -v /path/to/downloads:/downloads \
  -v /path/to/data:/sync \
  --restart unless-stopped \
  ghcr.io/linuxserver/resilio-sync

Parameters

Docker images 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.

Ports (-p)

Environment Variables (-e)

Volume Mappings (-v)

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

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.

User / Group Identifiers

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 user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Docker Mods

​​​ ​​​

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.

Support Info

• Shell access whilst the container is running:

  • docker exec -it resilio-sync /bin/bash

• To monitor the logs of the container in realtime:

  • docker logs -f resilio-sync

• Container version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' resilio-sync

• Image version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/resilio-sync

Versions

• 20.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.

• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.

• 11.02.19: - Rebase to bionic, add pipeline logic and multi arch.

• 05.02.18: - Add downloads volume mount.

• 28.01.18: - Add /sync to dir whitelist.

• 26.01.18: - Use variable for arch to bring in line with armhf arch repo.

• 15.12.17: - Fix continuation lines.

• 02.06.17: - Rebase to ubuntu xenial, alpine linux no longer works with resilio.

• 22.05.17: - Add variable for user defined umask.

• 14.05.17: - Use fixed version instead of latest, while 2.5.0 is broken on non glibc (alpine).

• 08.02.17: - Rebase to alpine 3.5.

• 02.11.16: - Initial Release.