I’m running syncthing in a Docker container (syncthing/syncthing) on OMV and after setting everything up it worked as expected.
But - after pulling a newer docker image from docker hub and/or restarting a container, the device ID for my OMV NAS is created new which means that I have to setup all shared folders on all connected devices again.
The config directory for docker syncthing is on a persistent path (not on a docker volume) and I thought that this means, that all configuration data is persistent as well. So - why do I get a new device ID when I restart the container or pull a new docker image?
But - the syncthing server does still know the shared folders and all other settings after pulling a new docker file or restarting the container. Why is a new device ID created and all other settings are the same as before the pull or the container restart?
Does anyone else have this behavior in docker syncthing?
OK, I think I solved it. It seems to be related to OMV’s docker plugin. If I update the docker image or restart the container via the plugin, then it seems to create a new device ID. If I update it via this script:
User syncthing (uid 1000, gid 100) has access to /home/syncthing/config where the config files are stored persistently. The network “syncthing” is a bridged network that is used by syncthing only.