Plugin not appearing for Docker about docker-volume-gluster HOT 4 CLOSED

Hi did you use docker plugin docker plugin install sapk/plugin-gluster (get from docker hub and run in a container) or use the binary docker-volume-gluster deamon ? In the last case, the plugin name is simply gluster.

from docker-volume-gluster.

From the information, I can confirm that you use the binary.

Plugins:
 Volume: cifs gluster local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog

Use that command to setup a volume and start a container with it:

docker volume create --driver gluster --opt voluri="<volumeserver>:<volumename>" --name test
docker run -v test:/mnt --rm -ti ubuntu

from docker-volume-gluster.

Great, it works now! Should I create a pull request to update the docs about this? It wasn't quite clear from the start

from docker-volume-gluster.

I was adding it to my todo list but please do.
For information, the readme need to indicate the first (new) part is "docker managed plugin" (https://docs.docker.com/engine/extend/) that is a image/container that is get from registry and contains the plugin and the needed configuration of container based on https://github.com/sapk/docker-volume-gluster/blob/master/config.json.
The old and second method, maybe more used for dev, is the legacy plugin definition by docker https://docs.docker.com/engine/extend/legacy_plugins/. It is the same binary that run inside the container one that you can directly execute on host (what you use).

Docker add also some confusion like docker plugin ls only listing managed plugin but the information of attached plugins is part of docker info

from docker-volume-gluster.