Antoine GIRARD

@Muscothym I must be that the volume was not mounted at the start. I need to take time to find a solution to report failure of mount but docker current...

Like suggested in #57 it seems to be a duplicate of #34

The first lines of the panic : ``` /usr/local/go/src/runtime/panic.go:513 +0x1b9 github.com/sapk/docker-volume-gluster/gluster/driver.parseVolURI(0x0, 0x0, 0x0, 0xe) /go/src/app/.gopath/src/github.com/sapk/docker-volume-gluster/gluster/driver/tools.go:74 +0x1c6 ```

Please see #44, on an other plugin I change how I managed management of volume but it introduce other bug when done with this one and haven't time to look...

I try to rework all my plugins to have a common base. But this is not currently working and haven't take time for this project so I set old as...

https://github.com/sapk/docker-volume-helpers

I would say it depends if it is a fix you can send it to old if a feature or want to make master work to master.

Great, I would gladly accept contribution. External point of view for documentation is really good. As maintainer I may assume a lot of things writing it. For start the docker...

You should be ok.

If you want to compile it just look at the makefile. I will show you how the plugin is compiled for both legacy (`make compile`) and managed (`make docker-plugin`) plugin....