docker-documentation/images/docker-syncthing.md

194 wiersze
9.5 KiB
Markdown
Czysty Zwykły widok Historia

2020-06-30 17:51:09 +00:00
# [linuxserver/syncthing](https://github.com/linuxserver/docker-syncthing)
[![GitHub Stars](https://img.shields.io/github/stars/linuxserver/docker-syncthing.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/linuxserver/docker-syncthing)
[![GitHub Release](https://img.shields.io/github/release/linuxserver/docker-syncthing.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/linuxserver/docker-syncthing/releases)
[![GitHub Package Repository](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=GitHub%20Package&logo=github)](https://github.com/linuxserver/docker-syncthing/packages)
2020-12-16 22:31:59 +00:00
[![GitLab Container Registry](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=GitLab%20Registry&logo=gitlab)](https://gitlab.com/linuxserver.io/docker-syncthing/container_registry)
2020-06-30 17:51:09 +00:00
[![MicroBadger Layers](https://img.shields.io/microbadger/layers/linuxserver/syncthing.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge)](https://microbadger.com/images/linuxserver/syncthing "Get your own version badge on microbadger.com")
[![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/syncthing.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=pulls&logo=docker)](https://hub.docker.com/r/linuxserver/syncthing)
[![Docker Stars](https://img.shields.io/docker/stars/linuxserver/syncthing.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=stars&logo=docker)](https://hub.docker.com/r/linuxserver/syncthing)
[![Jenkins Build](https://img.shields.io/jenkins/build?labelColor=555555&logoColor=ffffff&style=for-the-badge&jobUrl=https%3A%2F%2Fci.linuxserver.io%2Fjob%2FDocker-Pipeline-Builders%2Fjob%2Fdocker-syncthing%2Fjob%2Fmaster%2F&logo=jenkins)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-syncthing/job/master/)
2020-11-02 15:59:34 +00:00
[![LSIO CI](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=CI&query=CI&url=https%3A%2F%2Fci-tests.linuxserver.io%2Flinuxserver%2Fsyncthing%2Flatest%2Fci-status.yml)](https://ci-tests.linuxserver.io/linuxserver/syncthing/latest/index.html)
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
[Syncthing](https://syncthing.net) replaces proprietary sync and cloud services with something open, trustworthy and decentralized. Your data is your data alone and you deserve to choose where it is stored, if it is shared with some third party and how it's transmitted over the Internet.
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
## Supported Architectures
2019-02-05 19:09:56 +00:00
2019-09-03 07:33:40 +00:00
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
2019-02-05 19:09:56 +00:00
2020-11-02 15:59:34 +00:00
Simply pulling `ghcr.io/linuxserver/syncthing` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
The architectures supported by this image are:
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
| Architecture | Tag |
2020-06-30 17:51:09 +00:00
| :----: | --- |
2019-02-12 14:32:46 +00:00
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
2019-03-24 20:39:34 +00:00
| armhf | arm32v7-latest |
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
2019-02-12 14:32:46 +00:00
## Usage
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
Here are some example snippets to help you get started creating a container from this image.
2020-10-06 11:33:23 +00:00
### docker-compose ([recommended](https://docs.linuxserver.io/general/docker-compose))
2019-02-12 14:32:46 +00:00
Compatible with docker-compose v2 schemas.
```yaml
---
2020-04-07 17:51:05 +00:00
version: "2.1"
2019-02-12 14:32:46 +00:00
services:
syncthing:
2020-11-02 15:59:34 +00:00
image: ghcr.io/linuxserver/syncthing
2019-02-12 14:32:46 +00:00
container_name: syncthing
2020-09-16 00:54:26 +00:00
hostname: syncthing #optional
2019-02-12 14:32:46 +00:00
environment:
2019-03-05 16:32:46 +00:00
- PUID=1000
- PGID=1000
2019-02-12 14:32:46 +00:00
- TZ=Europe/London
volumes:
2020-09-16 00:54:26 +00:00
- /path/to/appdata/config:/config
- /path/to/data1:/data1
- /path/to/data2:/data2
2019-02-12 14:32:46 +00:00
ports:
- 8384:8384
- 22000:22000
2019-03-05 20:46:50 +00:00
- 21027:21027/udp
2019-02-12 14:32:46 +00:00
restart: unless-stopped
```
2019-02-05 18:51:16 +00:00
2020-10-06 11:33:23 +00:00
### docker cli
```
docker run -d \
--name=syncthing \
--hostname=syncthing `#optional` \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-p 8384:8384 \
-p 22000:22000 \
-p 21027:21027/udp \
-v /path/to/appdata/config:/config \
-v /path/to/data1:/data1 \
-v /path/to/data2:/data2 \
--restart unless-stopped \
2020-11-02 15:59:34 +00:00
ghcr.io/linuxserver/syncthing
2020-10-06 11:33:23 +00:00
```
2019-02-12 14:32:46 +00:00
## Parameters
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
### Ports (`-p`)
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
| Parameter | Function |
2020-06-30 17:51:09 +00:00
| :----: | --- |
2019-02-12 14:32:46 +00:00
| `8384` | Application WebUI |
| `22000` | Listening port |
| `21027/udp` | Protocol discovery |
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
### Environment Variables (`-e`)
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
| Env | Function |
2020-06-30 17:51:09 +00:00
| :----: | --- |
2019-03-05 16:32:46 +00:00
| `PUID=1000` | for UserID - see below for explanation |
| `PGID=1000` | for GroupID - see below for explanation |
2019-02-12 14:32:46 +00:00
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
### Volume Mappings (`-v`)
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
| Volume | Function |
2020-06-30 17:51:09 +00:00
| :----: | --- |
2019-02-12 14:32:46 +00:00
| `/config` | Configuration files. |
| `/data1` | Data1 |
| `/data2` | Data2 |
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
2020-09-16 00:54:26 +00:00
#### Miscellaneous Options
| Parameter | Function |
| :-----: | --- |
| `--hostname=` | Optionally the hostname can be defined. |
2020-06-30 17:51:09 +00:00
## Environment variables from files (Docker secrets)
2020-06-02 06:33:00 +00:00
You can set any environment variable from a file by using a special prepend `FILE__`.
As an example:
2020-06-30 17:51:09 +00:00
```
2020-06-02 06:33:00 +00:00
-e FILE__PASSWORD=/run/secrets/mysecretpassword
```
Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file.
## Umask for running applications
2020-06-30 17:51:09 +00:00
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
2020-04-28 17:51:12 +00:00
2019-02-12 14:32:46 +00:00
## User / Group Identifiers
2019-02-05 18:51:16 +00:00
2020-06-30 17:51:09 +00:00
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
2019-02-05 18:51:16 +00:00
2019-02-12 14:32:46 +00:00
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
2019-02-05 18:51:16 +00:00
2019-03-05 16:32:46 +00:00
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
2019-02-05 19:09:56 +00:00
2020-06-30 17:51:09 +00:00
```
2019-02-12 14:32:46 +00:00
$ id username
2019-03-05 16:32:46 +00:00
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
2019-02-12 14:32:46 +00:00
```
2019-02-05 19:09:56 +00:00
2019-02-12 14:32:46 +00:00
## Application Setup
2020-06-30 17:51:09 +00:00
**Note: ** The Syncthing devs highly suggest setting a password for this container as it listens on 0.0.0.0. To do this go to `Actions -> Settings -> set user/password` for the webUI.
2019-10-01 06:32:55 +00:00
2020-04-07 17:51:05 +00:00
## Docker Mods
2020-10-06 11:33:23 +00:00
[![Docker Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=syncthing&query=%24.mods%5B%27syncthing%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=syncthing "view available mods for this container.") [![Docker Universal Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=universal&query=%24.mods%5B%27universal%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
2020-04-07 17:51:05 +00:00
2020-10-06 11:33:23 +00:00
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
2020-04-07 17:51:05 +00:00
2019-02-12 14:32:46 +00:00
## Support Info
2019-09-03 07:33:40 +00:00
* Shell access whilst the container is running:
2019-02-12 14:32:46 +00:00
* `docker exec -it syncthing /bin/bash`
2019-09-03 07:33:40 +00:00
* To monitor the logs of the container in realtime:
2019-02-12 14:32:46 +00:00
* `docker logs -f syncthing`
2019-09-03 07:33:40 +00:00
* Container version number
2019-02-12 14:32:46 +00:00
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' syncthing`
* Image version number
2020-11-02 15:59:34 +00:00
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/syncthing`
2019-02-12 14:32:46 +00:00
## Versions
2021-01-29 20:11:14 +00:00
* **29.01.21:** - Deprecate `UMASK_SET` in favor of UMASK in baseimage, see above for more information.
2021-01-29 17:43:57 +00:00
* **23.01.21:** - Rebasing to alpine 3.13.
2020-09-16 00:54:26 +00:00
* **15.09.20:** - Use go from alpine edge repo to compile. Remove duplicate UMASK env var. Add hostname setting.
2020-07-03 14:35:29 +00:00
* **01.06.20:** - Rebasing to alpine 3.12.
2019-12-27 11:00:48 +00:00
* **19.12.19:** - Rebasing to alpine 3.11.
2019-07-05 19:59:55 +00:00
* **28.06.19:** - Rebasing to alpine 3.10.
2019-03-24 20:39:34 +00:00
* **23.03.19:** - Switching to new Base images, shift to arm32v7 tag.
2019-03-05 20:46:50 +00:00
* **05.03.19:** - Update Build process for v1.1.0 release.
2019-02-25 03:38:42 +00:00
* **22.02.19:** - Rebasing to alpine 3.9.
2019-02-12 14:32:46 +00:00
* **16.01.19:** - Add pipeline logic and multi arch.
* **30.07.18:** - Rebase to alpine 3.8 and use buildstage.
* **13.12.17:** - Rebase to alpine 3.7.
* **25.10.17:** - Add env for manual setting of umask.
2020-06-30 17:51:09 +00:00
* **29.07.17:** - Simplify build structure as symlinks failing on > 0.14.32
2019-02-12 14:32:46 +00:00
* **28.05.17:** - Rebase to alpine 3.6.
* **08.02.17:** - Rebase to alpine 3.5.
* **01.11.16:** - Switch to compiling latest version from git source.
* **14.10.16:** - Add version layer information.
* **30.09.16:** - Fix umask.
* **09.09.16:** - Add layer badges to README.
* **28.08.16:** - Add badges to README.
* **11.08.16:** - Rebase to alpine linux.
2020-06-30 17:51:09 +00:00
* **18.12.15:** - Initial testing / release (IronicBadger)
* **24.09.15:** - Inital dev complete (Lonix)