# New Synology DSM 7 | Syncthing package for Synology NAS
**URL:** https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702
**Category:** Development
**Created:** [October 7, 2020, 6:00am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702 "2020-10-07T06:00:53Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [October 7, 2020, 6:00am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/1 "2020-10-07T06:00:53Z")
> [@New package for Synology NAS](https://forum.syncthing.net/t/new-package-for-synology-nas/14396/141):
>
> I use VMM on a DS and [Virtual DSM 7.0 Preview](https://global.download.synology.com/download/DSM/beta/7.0/40850/DSM_VirtualDSM_40850.pat). There is a change in the installation process in the new DSM 7.0, which usually runs in the future no longer as root, instead as user in the new lower privilege framework. In DSM 7.0 in the package center both packages are available: [Syncthing\_DSM7-4] If I try to install the Safihre package (SynoCommunity), I got the follow message (sorry for the german): [Syncthing\_DSM7-3] This means: If I try to install…
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.
```
---
### Author:  [@imsodin](https://forum.syncthing.net/u/imsodin)
#### Post date: [October 7, 2020, 6:55am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/2 "2020-10-07T06:55:59Z")
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.
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 9, 2020, 10:21am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/3 "2020-12-09T10:21:44Z")
Yesterday the DSM 7 Beta has released and during the update the follow mark arise (sorry for german):
The “Artikel” means
> **[DiskStation Manager - Knowledge Base | Synology Inc.](https://www.synology.com/de-de/knowledgebase/DSM/tutorial/Third_Party/supported_third_party_packages_beta)**
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 9, 2020, 11:47am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/4 "2020-12-09T11:47:05Z")
I updated my VMM from DSM 7 from Preview to Beta with the same result as expected:
.
.
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 9, 2020, 6:48pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/5 "2020-12-09T18:48:52Z")
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 ?
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 11:07am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/6 "2020-12-30T11:07:17Z")
I managed to get SyncThing running smoothly on DSM7 using Docker. This is clearly way forward.  
---
### Author:  [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [December 30, 2020, 11:18am UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/7 "2020-12-30T11:18:42Z")
If that works well it sounds like a good migration path.
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 2:14pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/8 "2020-12-30T14:14:44Z")
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.
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 2:36pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/9 "2020-12-30T14:36:47Z")
> [@Andy](#):
>
> When I synchronize files, they are created twice, in the container and in the data directory on the server.
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…
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 2:42pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/10 "2020-12-30T14:42:56Z")
My opinion is, in your case you have data in e.g. photo and photosync.
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 2:47pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/11 "2020-12-30T14:47:28Z")
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”
- Volumes as you require - beware of privileges on the folders…
- also don’t forget to put /var/syncthing folder “out” of Docker image, **otherwise you will loose all your settings when updating image…**
- Change the P-UID and P-UID if required (I’m lazy … so I keep it running within Root which is NOT secure)
_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 😉**
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 2:50pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/12 "2020-12-30T14:50:40Z")
> [@Andy](#):
>
> My opinion is, in your case you have data in e.g. photo and photosync.
Not really, in my case /photosync is just MOUNT path - a “pointer” to real directory.
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 2:55pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/13 "2020-12-30T14:55:35Z")
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?
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 3:00pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/14 "2020-12-30T15:00:28Z")
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.
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 3:03pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/15 "2020-12-30T15:03:14Z")
You need the config also outside, since you need a Update of the Image, all database data are lost.
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 3:06pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/16 "2020-12-30T15:06:16Z")
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 😉
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 3:07pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/17 "2020-12-30T15:07:16Z")
> [@shaarkys](#):
>
> in my case /photosync is just MOUNT path - a “pointer” to real directory
What is the exact command for that? Doe you need a bootscript for that?
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 3:08pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/18 "2020-12-30T15:08:21Z")
> [@shaarkys](#):
>
> to recompile Syncthing package for DSM 7.0
But needs much more effort. The SPK is much easier to handle.
---
### Author:  [@shaarkys](https://forum.syncthing.net/u/shaarkys)
#### Post date: [December 30, 2020, 3:10pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/19 "2020-12-30T15:10:42Z")
This is given just via the settings…see my HOW-TO above. No bootscript or anything is required.
---
### Author:  [@Andy](https://forum.syncthing.net/u/Andy)
#### Post date: [December 30, 2020, 3:20pm UTC](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702/20 "2020-12-30T15:20:18Z")
> [@shaarkys](#):
>
> in my case /photosync is just MOUNT path - a “pointer” to real directory
It means `MOUNT /photosync -a` I have understood.
[Next page](https://forum.syncthing.net/t/new-synology-dsm-7-syncthing-package-for-synology-nas/15702.md?page=2)