Search the Community

Showing results for tags 'docker'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 12 results

  1. I've installed Resilio natively from website using manual package download (apollolake), but also tried using official docker image (, both have a 'problem' that after a short window the sync speed caps at around 1-2mb/s. After installing the docker version I happened to increase the ram allocation just trying things that might help and it did, straight way I was getting 20-30mb/s HURRAY! Well I was celebrating too soon, as the next file I tested was back to 1-2mb/sec, looking at the docker overview you can see the ram usage slow rise from 0 to ~10gb (I'd se
  2. Hi, 2.5.13 It seems that the docker version is limited to LAN when not used with --net host argument? is that correct? I guess that's not a docker limitation since i can run a webserver from docker without using this argument and it's not a firewall problem nor a router problem... So did you code Sync like that? Why would it not link primarly with one of your relay server then look for others on the subnet ? So I've consulted your FAQ about your network protocol: So if I'm following this. For docker it's a bit broken since you force users to use port
  3. Hello, I'm running Resilio Sync using the official Docker image (resilio/sync). I can access the UI on port 8888 and everything looks ok. Unfortunately, I receive a 404 for the following resources: /gui/css/style.css /gui/version.json?1521721548733 This makes the UI completely unresponsive. For instance, I can't link any device because the "Link Device" link is broken. I'm a PRO customer.
  4. Hi, I am using the Official Docker container and have multiple mounted_folders setup, for the sake of debugging i will limit that to one. The container is launched via docker-compose, the volume is mounted at launch /start and i can access it with the UI and write data in there (read sync a folder), but all files have root:root ownership. Any idea how to get the ownership of the file within this folder to be the same as the parent mounted folder ? --- According to Docker discussions, the volume will have ownership of the user in the container (which seems to be
  5. Hi, I would like to know if it would be better to use the nas version directly on a nas as synology or qnap / OR use the docker version for those who can run docker on their nas ? thanks in advance
  6. Hi Resilio Team Like others in this forum who do embedded Linux builds I need a musl compiled sync client as well. Since docker will switch its default to alpine Linux (that is musl based) [1] I suggest you should seriously consider offering a static compiled binary. If you client is written in golang this is very easily achievable[2]. Of course opensourcing the client would help as well :D. Thanks for your time. Joe [1] [2]
  7. Hi, Are you going to provide a command-line interface for BTSync 2.0? Or an API compatible with 2.0 folders? Or at least a way to deal with 2.0 folders with config file? I love BitTorrent Sync. But I used to deploy peers using Docker containers, it was super easy. Now I can't sync the new folders (2.0) without going through the web GUI... In some use cases, it's not even an option. Right now it seems like I have to keep working with 1.4 folders...
  8. There are also Alpine-based images , but this is not for Alpine fans, as the images are based on Slitaz linux. The result images are quite small (24MB for the latest version 2.4.1). See image attached. Disclaimer: These images are 32-bit versions because my base image `icymatter/slitaz40-minimal` is an 32-bit image) Images on Dockerhub: ( * 1.3: icymatter/slitaz40-btsync13 * 1.4: icymatter/slitaz40-btsync14 * 2.4: icymatter/slitaz40-btsync24 Hope this helps
  9. I just setup resilio on two Macs and a iPhone and everything is in sync. Today i tried my server and used the official docker container. However after around half of my files synced the website is not accessible anymore. My (upload) client recognises no more available peers. Attaching to the container or restarting is not possible, i have to restart docker to gain access to the container. However after 1 or 2 minutes of syncing the connection is lost again and the container is unresponsive. The logs right when the connection is lost: Show/hide second try after docker resta
  10. Hi all, I have troubles automatically syncing directories in my user context with having the Sync instance encapsulated in a Docker container (having a Pro licence) Using the Sync-Dockerfile [1] [2] (afais Ubuntu 15.04), I have setup an instance on a Ubuntu based server and anothe rinstance on my Fedora 23 desktop. the server's data directory points to a btrfs subvolume, i.e., DATA_FOLDER="/data/sync/" > docker run -d --name Sync -p$WEBUI_PORT:8888 -p 55555 -v $DATA_FOLDER:/mnt/sync --restart on-failure bittorrent/sync on the desktop
  11. Guest

    Btsync As Docker

    hi, I am running rockstor as my NAS, they use docker to run btsync, which is quite nice. nevertheless they lack updating the docker container to the latest version. my question now, why does the sync team not providing docker images with the latest version as they do for linux, windows, mac osx and other platforms and systems? for some NAS systems this would make it so much easier to adopt the official docker image to their installations. thanks for any hints
  12. Hey! I'm trying to create bittorrent volume with docker. It runs perfectly with root but running btsync with root doesn't keep file ownerships in place. So I build small bash script which detects ownership and creates new user with same uid&gid as files before starting btsync. When i try to run btsync with this new user $ sudo -H -u btsync bash -c 'btsync --config /btsync/config --nodaemon' I get this: btsync: /mnt/jenkins/workspace/Build-Sync-x64/linux/breakpad/client/linux/handler/minidump_descriptor.h:55: google_breakpad::MinidumpDescriptor::MinidumpDescriptor(const string&):