SOLVED Syncthing not starting if share Samba/NFS is mounted

Marco79

Cadet
Joined
Feb 11, 2023
Messages
5
Hello verybody!

I installed the Syncthing App (tried with both standard & Truecharts).

Set it up mounting 2 Datasets inside the app config.

After that I shared (Samba + NFS) the share.

Everything OK, since I restart the app.

If I start the kubernetes app after mounting the Samba/NFS share of the foder in sync the app wont start…



image
image1508×403 21.8 KB



It sits there “deployng” forever.

If I simply turn off the shares and restart the aapp, it starts and then I can turn on the share (after deployng) without any problems…

Ther is a way to make it start up with the folders shared and mounted in Syncthing?

Maybe a script to unmount - deploy - mount the shares??

Thanks a lot everyone!!!

Marco
 

Belperite

Dabbler
Joined
Feb 21, 2023
Messages
26
Yes this is the well-known "host path validation" issue that has been discussed quite a lot on this forum :) Share your folder/filesystem using NFS as well as SMB, then use the Truecharts version of syncthing and configure it to mount the NFS share (not using host path).
 

Marco79

Cadet
Joined
Feb 11, 2023
Messages
5
Yes this is the well-known "host path validation" issue that has been discussed quite a lot on this forum :) Share your folder/filesystem using NFS as well as SMB, then use the Truecharts version of syncthing and configure it to mount the NFS share (not using host path).
Thanks a lot!

I tried your suggestion:

1677865916704.png


but I cannot start it anyway (deploying).

1677865968378.png


Thanks a lot for any help.

Marco
 

Marco79

Cadet
Joined
Feb 11, 2023
Messages
5
The issue was here:

1677916542935.png


I now have inserted "root" under Maproot User and "wheel" under Maproot Group on the NFS shares and everything is working!


Thanks a lot!
 
Joined
Apr 17, 2023
Messages
3
Hi, I am at the same point now and tried your suggestion to maproot-user and maproot-group. The result stays the same.
And is it okay to use "localhost" here? I thought that would result in the kubernetes-pod using its kubernetes-network-IP and not the host-machines.
I am thankful for any ideas fixing this.

Kind regards, Lukas
 
Top