New Synology DSM 7 | Syncthing package for Synology NAS

T connect to the above issue, from the Synology development I got the follow message:

Hi Andreas,

May I know if all's going well for DSM7.0's package development?

In addition, it's reflected by some of our users that the current version of Syncthing in our Package Center seems to wrongly write files constantly and excessively into system partition, which leads to DSM upgrade failures due to Syncthing taking up all remaining storage space in the system partition.

This problem occurs when:

1. Attach USB and generate USBshare.

2. Use 3rd-party backup package "Syncthing".

3. Remove USB device.

4. After unmounting the usbshare, "Syncthing" still writes data into the original path. ( **/volumeUSB1/usbshare1-1/** )

Please let us know if there's any recommended solution to this problem.

Meanwhile, due to internal organisational adjustments, please allow me to introduce Vanessa, our new contact window for 3rd-Party integration matters.

She will be taking over from now on and assist you with all future procedures.

Thank you for your support!

Best regards,

Charles Shih

Product Specialist
+886-2-2955-1814 #8802
**Syno** logy Inc.

If “they” (whoever that really is in the end) have a problem they can come talk to us here on the forum to get help like everyone else. Doing support through possibly multiple intermediaries is definitely a show-stopper.

Yesterday the DSM 7 Beta has released and during the update the follow mark arise (sorry for german):

grafik

The “Artikel” means

I updated my VMM from DSM 7 from Preview to Beta with the same result as expected:

.

.

That’s really unpleasant surprise, I miss somehow information on root restrictions in beta release log… ;-( I guess there isn’t any workaround, eg. by installing via SSH ?

I managed to get SyncThing running smoothly on DSM7 using Docker. This is clearly way forward.

1 Like

If that works well it sounds like a good migration path.

Syncthing for Docker is not a final solution for my case for various reasons.

When I synchronize files, they are created twice, in the container and in the data directory on the server. If this “double occupancy” can be avoided, I would be happy to learn more.

I find the administrative effort of storing all possible directories in the Docker configuration high. This is justifiable for a few directories, but not for around 60, as in my case.

Hm, I’m not sure I follow. By Volume settings and directory mapping, like on example below, you get no duplication, those are just mount points…

obrazek

1 Like

My opinion is, in your case you have data in e.g. photo and photosync.

Maybe if that would help to someone, here is my how-to :

  • download and install Docker package
  • navigate to registry and select appropriate container , witch version you prefer - on the image below is my own preference

  • configure container accordingly, eg.

  • I set ports to the defaults, otherwise they are “random” obrazek

  • Volumes as you require - beware of privileges on the folders… obrazek

  • also don’t forget to put /var/syncthing folder “out” of Docker image, otherwise you will loose all your settings when updating image… obrazek

  • Change the P-UID and P-UID if required (I’m lazy … so I keep it running within Root which is NOT secure)

obrazek

Also one part is missing - Network bridge - you may use Bridge (simply associate it with container) or Host network but then things might get slightly different.

…then start container and you may navigate to GUI on usual address.

Please note, this “How-To” is not perfect. If you don’t know what you are doing, don’t blame me for data loss and better wait for new updated package :wink:

1 Like

Not really, in my case /photosync is just MOUNT path - a “pointer” to real directory.

I understand, that “photo” is the standard Synology photo directory. So you have configured, that photosync links to photo, so at the end is 1 directory.

If this the case, in which are the container files with database etc. which is in the “config” directory?

I’m not expert on SyncThing but I would say it’s within /var/syncthing directory and even in this case you may redirect and reconfigure it to be used outside of container. You can play with that and further analyse on the Terminal of given Container, in my case sh (shell) works just fine.

You need the config also outside, since you need a Update of the Image, all database data are lost.

Indeed but it’s still matter of configuration and best way to do that. Still it was much more doable for me then to recompile Syncthing package for DSM 7.0 :wink:

What is the exact command for that? Doe you need a bootscript for that?

But needs much more effort. The SPK is much easier to handle.

This is given just via the settings…see my HOW-TO above. No bootscript or anything is required.

It means MOUNT /photosync -a I have understood.