Allow support for NFS/CIFS volume mount (Useful for swarm modes)

What problem will this feature address?

I'm always frustrated that there is no easy way to configure external volume mounts based on network attached storage.

Describe the solution you'd like

Allow the admin to configure the following features

• Docker volume destination

User permission can also be tied to the said volume destination (Linked to issue: #788 )

The volume destination can be something like the following:

• Local
• Remote

For remote we have options such as: nfs, glusterfs, iscsi, sshfs, cifs, etc.

Describe alternatives you've considered

Creating docker volume manually and linking them

For example:

docker volume create --driver local \
  --opt type=nfs \
  --opt o=addr=[ip-address],rw \
  --opt device=:[path-to-directory] \
  [volume-name]

Additional context

Docker run command referenced from: https://phoenixnap.com/kb/nfs-docker-volumes

Will you send a PR to implement it?

Maybe (Need help)

Start by tracing the existing Docker volume configuration and creation flow; the issue names no files or tests. Compare the current model with the requested local and remote destinations, including NFS and CIFS options. Done should provide an admin-configurable way to create or use these network-backed volumes without manual Docker commands.