Open dippynark opened 4 years ago
When i did initial mount tests, i saw somewhere in the documentation or configuration files that the prefix colon was there and so it has been there since. I'll build a test image for that PR and test it.
From the rclone documentation:
:backend:path/to/dir
This is an advanced form for creating remotes on the fly. backend should be the name or prefix of a backend (the type in the config file) and all the configuration for the backend should be provided on the command line
So, as it stands, the remote
volume attribute in csi-rclone doesn't specify a remote as defined in rclone.conf
, but rather a backend, and should probably be renamed to reflect this.
The colon prefix here prevents the node agent from finding my mount configuration in my rclone.conf - is it really needed?
The rclone mount usage command doesn't include it:
Removing the colon and recompiling (e.g. https://github.com/dippynark/csi-rclone/pull/1/files) works great!