There is a very common phrase here: Users always end up doing something unforeseen.
I don't think anyone would think to configure docker directories in a remote folder, and honestly, I think it's a bad idea for many reasons. But if you insist on doing it, the problem you have is that the plugin is trying to configure root permissions on the remote resource.
Thanks for the reply.
I get what you are saying with regards running docker remotely, but I just want to run a couple of non-critical workloads - Portainer, Speedtest tracker et al for testing purposes.
If there are issues, then I'll likely assess whether it is worth me spending hundreds of £'s on a NAS that supports docker, or DAS storage for my Raspberry Pi OMV server.
Having said all that, I have been using docker on an EC2 instance in AWS as and when required for study purposes, for a good while with out issue....
You mentioned the root permissions for the plugin - can you provide some extra explanation on what is required please?
Thanks