I'm using Dazzle to configure a SparkleShare host on a RPi that has an NFS mount with root squashed. I setup Dazzle with a home directory of /home/sparkle/, sync its files to a sparkle owned directory in the NFS mount and then bind mount that back over the spark home so that my sparkleshare is NFS backed (so it get's the benefit of all my NAS features).
However, since root is squashed, dazzle link fails with this configuration. Root can't write the ssh-key to the authorized keys. The script also bombs out if I try to run it as sparkle, who actually owns the files. I had to manually edit the authorized_keys file and add my client ID, and this worked.
So it doesn't appear that root is required for dazzle link. Is it possible to remove that requirement, and possibly remove it from any other dazzle command that claims to require it but does not?
I'm using Dazzle to configure a SparkleShare host on a RPi that has an NFS mount with root squashed. I setup Dazzle with a home directory of
/home/sparkle/, sync its files to asparkleowned directory in the NFS mount and then bind mount that back over the spark home so that my sparkleshare is NFS backed (so it get's the benefit of all my NAS features).However, since root is squashed,
dazzle linkfails with this configuration. Root can't write the ssh-key to the authorized keys. The script also bombs out if I try to run it assparkle, who actually owns the files. I had to manually edit theauthorized_keysfile and add my client ID, and this worked.So it doesn't appear that root is required for
dazzle link. Is it possible to remove that requirement, and possibly remove it from any other dazzle command that claims to require it but does not?