Signed-off-by: Lei Jitang [email protected]

This is a original design of support multiple volume driver on docker run/create cli and waiting for some feedback from the community.
The driver should be a part of volume identifier, I think the user should aware what driver the volume used, since different driver have different feature and store the data in different place. In this way user can use multiple volume driver in a single docker run/create cli and
different volume driver can have the same volume name.
Use the sytax name@driver:/dest as the volume identifier as @srust 's proposal.
Here is the example.

[lei@fedora ~]$ docker run -v test@convoy:/data -v test:/test busybox
[lei@fedora ~]$ docker volume ls
DRIVER              VOLUME NAME
convoy              test
local               test

If no driver specified in the volume identifier, use default driver which is specified by --volume-driver, if no, use default local
the docker volume cli should use name@driver, if no driver specified, use default local

[lei@fedora ~]$ docker volume inspect test
[
    {
        "Name": "test",
        "Driver": "local",
        "Mountpoint": "/var/lib/docker/volumes/test/_data"
    }
]
[lei@fedora ~]$ docker volume inspect test@convoy
[
    {
        "Name": "test",
        "Driver": "convoy",
        "Mountpoint": "/var/lib/convoy/devicemapper/mounts/0f1c1fc2-21e3-4f83-99b1-9c23b9be649b"
    }
]

For more information see #15997