A syncthing Docker container.
This container is intended to be run on a server that will be shared by
a group of people. Although this container can be used on a personal
workstation, it will not be very convenient. It's best to download a native
distribution for your machine from Syncthing.
Video: Syncthing Overview and Demo
<a href="http://www.youtube.com/watch?feature=player_embedded&v=ycVM5pdH3xg" target="_blank"><img src="http://img.youtube.com/vi/ycVM5pdH3xg/0.jpg" alt="Syncthing Overview and Demo" width="240" height="180" border="10" /></a>
Building the image
docker build -t ptimof/syncthing
Or just pull the latest from Docker Hub:
docker pull ptimof/syncthing
Host system preparation
On the host machine, create the user and group
GID of 800:
groupadd -g 800 syncthing useradd -m -u 800 -g 800 syncthing
If 800 is already taken, or a different
GID is desired, the Dockerfile
groupadd commands will need to be modified to match.
Creating the container
docker create --name syncthing -p 8080:8080 -p 22000:22000 -p 21025:21025/udp -v /home/syncthing:/home/syncthing ptimof/syncthing
Running the container
syncthing is more intended as a personal file syncing system, configuration
is more like an application on a PC than a sysadmin-controlled machine.
Config files are located in
~/syncthing/.config/syncthing, and files of note are:
config.xml: the main configuration file
cert.pem: TLS files
This directory must be writable by the
syncthing user on the host computer.
Running for the first time
The very first run on a host system of this container will create two directoryies:
At this point, there are no active shares, but the admin UI is exposed to any IP,
and has no password. The very first activity that should immediately be done is
to set a username/password for the UI.
To run the admin UI, use a browser to connect to
Dockerfile is configured to allow passing arguments directly to
Documentation on configuring
syncthing is scarce (it is early in it's development
cycle). There should be no need to change the command line parameters as they stand,
however config and environment parametsr can be gleaned from the source for
config.xml file, on the otherhand, appears to have a few tags that are not controlled
by the admin UI. The best place to decode this is on the