Is there an existing issue for this?
Current Behavior
The current Syncthing image is still on 2.1.3, and it looks like the CI pipeline is detecting Syncthing 2.1.5 but failing while building it.
The build log shows:
go: go.mod requires go >= 1.26.2 (running go 1.25.10; GOTOOLCHAIN=local)
It appears the Alpine build environment currently installs Go 1.25.10, while Syncthing 2.1.5 requires Go >= 1.26.2.
CI pipeline:
https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-syncthing/job/master/
The version detection itself seems to be working correctly; the failure occurs during compilation, so the updated image never gets published.
Current published LinuxServer image:
Upstream:
It looks like the build environment/toolchain needs to be updated to Go 1.26.2 or newer.
Expected Behavior
No response
Steps To Reproduce
- Open the LinuxServer Syncthing Jenkins pipeline.
- Run or inspect the latest build for
master.
- The build detects Syncthing
v2.1.5.
- Compilation fails because the build environment has Go 1.25.10 while Syncthing requires Go >= 1.26.2.
Environment
- OS:
- How docker service was installed:
CPU architecture
x86-64
Docker creation
Not applicable.
The failure occurs in the LinuxServer CI build pipeline before a new Docker image is successfully created or published.
Container logs
Not applicable.
There are no container logs because the affected `v2.1.5` image is not successfully built/published. The relevant logs are the Jenkins build logs.
Is there an existing issue for this?
Current Behavior
The current Syncthing image is still on 2.1.3, and it looks like the CI pipeline is detecting Syncthing 2.1.5 but failing while building it.
The build log shows:
It appears the Alpine build environment currently installs Go 1.25.10, while Syncthing 2.1.5 requires Go >= 1.26.2.
CI pipeline:
https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-syncthing/job/master/
The version detection itself seems to be working correctly; the failure occurs during compilation, so the updated image never gets published.
Current published LinuxServer image:
Upstream:
It looks like the build environment/toolchain needs to be updated to Go 1.26.2 or newer.
Expected Behavior
No response
Steps To Reproduce
master.v2.1.5.Environment
CPU architecture
x86-64
Docker creation
Not applicable. The failure occurs in the LinuxServer CI build pipeline before a new Docker image is successfully created or published.Container logs
Not applicable. There are no container logs because the affected `v2.1.5` image is not successfully built/published. The relevant logs are the Jenkins build logs.