Yesterday the DSM 7 Beta has released and during the update the follow mark arise (sorry for german):
The “Artikel” means
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 ?
1 Like
If that works well it sounds like a good migration path.
1 Like
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…
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”
-
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 
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
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.
You don’t have to execute anything within Docker container, this is already secured by the Docker image config as such, as I mentioned on the screenshots.
Eg. just by following configuration I mentioned above, when CHECKING my mounts on the container :
Btw thanks for pointing out config - I just tested it with /var/syncthing outside of Docker on my NAS and seems to be working fine so far (updated HowTo) (…and updated HyperBackup to include this directory in my backups )
2 Likes
It seems e.g. photosync is a folder inside of the container. Is possible to see the content and size?