BitTorrent Sync (deprecated)
Please note, that this image is outdated and is no longer supported and will stay with Sync version 2.3.8. For supported version please use Resilio Sync image. New Github repository can be found here.
Sync uses peer-to-peer technology to provide fast, private file sharing for teams and individuals. By skipping the cloud, transfers can be significantly faster because files take the shortest path between devices. Sync does not store your information on servers in the cloud, avoiding cloud privacy concerns.
DATA_FOLDER=/path/to/data/folder/on/the/host WEBUI_PORT=[ port to access the webui on the host ] mkdir -p $DATA_FOLDER docker run -d --name Sync \ -p 127.0.0.1:$WEBUI_PORT:8888 -p 55555 \ -v $DATA_FOLDER:/mnt/sync \ --restart on-failure \ bittorrent/sync
Go to localhost:$WEBUI_PORT in a web browser to access the webui.
If you do not want to limit the access to the webui to localhost, run instead:
docker run -d --name Sync \ -p $WEBUI_PORT:8888 -p 55555 \ -v $DATA_FOLDER:/mnt/sync \ --restart on-failure \ bittorrent/sync
If you need to mount extra directories, mount them in /mnt/mounted_folders:
docker run -d --name Sync \ -p 127.0.0.1:$WEBUI_PORT:8888 -p 55555 \ -v $DATA_FOLDER:/mnt/sync \ -v <OTHER_DIR>:/mnt/mounted_folders/<DIR_NAME> \ -v <OTHER_DIR2>:/mnt/mounted_folders/<DIR_NAME2> \ --restart on-failure \ bittorrent/sync
Do not create directories at the root of mounted_folders from the Sync webui since this new folder will not be mounted on the host.
- /mnt/sync - State files and Sync folders
- 8888 - Webui
- 55555 - Listening port for Sync traffic
is there a way to store the configuration files on the Host, so that I can move it from one host to another?
It works and is up2date with current official version (which as the time of writing is 2.2.7)
Is it generally expected for this to be a memory hog when syncing for the first time? Currently sitting at 11GB memory used by this container.
The dockerfile as well as a link to the sourcecode is available. What do you mean?
It'd be great if you can publish the Dockerfile source (along with your run_sync script) on Github. It'll be easier for contributors to submit patches.
Build fails. Whats wrong?