Public | Automated Build

Last pushed: 19 minutes ago
Short Description
Open Source Continuous File Synchronization
Full Description

Please ignore the Docker Hub "Source Repository" and "Dockerfile" -- they are incorrect; automated builds cannot be switched between repos, so this is built/pushed from my own CI server via instead.


See Dockerfile and example script for usage.


In the inotify tags, you'll find syncthing-inotify.

This image is only useful in the context of a running instance of syncthing, so check out the main image tags if you don't have syncthing already.

You probably also want to read "Troubleshooting for folders with many files on Linux", especially sudo sysctl -w fs.inotify.max_user_watches=204800 (as the temporary not-safe-from-reboot solution).

Docker Pull Command
Source Repository

Comments (2)
2 years ago

Running as user prevents auto-update. Is this intentional?

2 years ago


when run this container in coreos, the port can't be exposed to the coreos host, with following adapted script(have to run the script with sudo).

set -e

if [ "$HOME" = '/home/user' ]; then
    echo >&2 'uh oh, HOME=/home/user'
    exit 1

mkdir -p "$HOME/.config/syncthing"

set -x
#    -v /etc:/host/etc \
docker run -d \
    --name syncthing \
    --restart always \
        -p 8384:8384 \
    -u "$(id -u):$(id -g)" \
    -v "$HOME:$HOME" \
    -v "$HOME/.config/syncthing:/home/user/.config/syncthing" \
    --net host \
    tianon/syncthing "$@"
timeout 10s docker logs -f syncthing || true

I tried with a different container(not syncthing), port is exposed as expected and I can visit the web page perfectly.

What's your suggestion, please? In coreos shell, wget http://localhost:8384/ can get the page, but just can't visit it in my windows where coreos is started with vagrant, tried the combination of all listed ips in coreos.

Of course, it works perfectly when run it on a debian host.