readystack/syncthing repository overview

⁠Syncthing

readystack/syncthing:v2.1.7-CE-ubuntu24.04-r2

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/syncthing/recipe⁠
• Upstream source at this release's pinned commit (v2.1.7): https://github.com/syncthing/syncthing/tree/d6d0181f7d466381c4b39ec8fd944c364f939b32⁠
• Product page: https://readystack.dev/products/syncthing⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/syncthing⁠
• Release history (JSON): https://readystack.dev/api/releases/syncthing⁠
• Defect record: https://readystack.dev/defects.html?product=syncthing⁠
• Today's scan: https://readystack.dev/products/syncthing#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=syncthing⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/syncthing/syncthing v2.1.7 (MPL-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Individuals and small teams who want files synced between their own computers without a cloud service in between.

Why: Syncthing continuously synchronises files between two or more computers in real time over encrypted, authenticated connections, with no central server that stores the data.

Use case: A photographer edits on a desktop at home and travels with a laptop. Syncthing keeps the project folders on both in sync whenever the two can reach each other, so the latest edits are on whichever machine is at hand, and the files are never stored on anyone else's server.

About the upstream project, written from its own description: https://github.com/syncthing/syncthing⁠ · https://syncthing.net/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:4ff206218425e119d5b898c6ad4924795869272d6b883f61afe2144fc1f6f0c4 on 2026-10-27.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/syncthing⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:4ff206218425e119d5b898c6ad4924795869272d6b883f61afe2144fc1f6f0c4; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/syncthing:v2.1.7-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (syncthing).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v2.1.7-CE-ubuntu24.04-r2 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/syncthing:v2.1.7-CE-ubuntu24.04-r2

# ✗ unsupported (do not pull)
docker pull readystack/syncthing:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/syncthing:v2.1.7-CE-ubuntu24.04-r2 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container running syncthing (pure-Go, CGO-free) as the non-root syncthing user (uid 999); syncthing's own monitor process is PID 1 and runs the syncthing worker. Continuous peer-to-peer file synchronization. State lives under STHOMEDIR (/var/syncthing/config): config.xml, the device identity (cert.pem/key.pem), the GUI HTTPS certificate, and the folder indexes in an embedded pure-Go SQLite database under index-v2/ (main.db plus one folder.*.db per folder). No external database server, no docker-compose, no Kubernetes. The image is the complete running instance.

docker run -d --name syncthing -p 8384:8384 -p 22000:22000/tcp -p 22000:22000/udp -p 21027:21027/udp -v st-config:/var/syncthing/config readystack/syncthing:v2.1.7-CE-ubuntu24.04-r2

On first start the web GUI on port 8384 asks for user admin and a generated password: read it with docker exec syncthing cat /var/syncthing/config/initial_gui_password, or set SYNCTHING_GUI_USER / SYNCTHING_GUI_PASSWORD before the first start. Scripts use the API key from config.xml (the element under ).

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/syncthing⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:41018e6c100e3c14eb410fae22c814174709c3846023858d7368ea50c3fae352 on 2026-10-27.

— ReadyStack · readystack.dev