VolumeDriver.Mount: exit status 1 about docker-volume-gluster HOT 12 OPEN

@badele That normal, the plugin does have to resolve nodename of volume (node-1, node-2, node-...) but those names are only resolved by docker inside the same network.

I can recommend you to replace nodename by there respectives IP at volume creation. gluster volume create dockerstore replica 3 IP-node-1:/data/glusterfs/store/dockerstore IP-node-2:/data/glusterfs/store/dockerstore IP-node-3:/data/glusterfs/store/dockerstore (Note: you can keep nodename for peer probe)

This is how gluster works when you mount it, the client will retrieve the configuration (node-1:/data/glusterfs/store/dockerstore node-2:/data/glusterfs/store/dockerstore ...) but gluster can't outside the docker network (on host or in plugin container) resolve those names. A other solution is to add node-X container ip to host file /etc/hosts to resolve those names.

If you want, I setup the same type of configuration for integration testing. Just clone the repo and do
make test-integration (code here : https://github.com/sapk/docker-volume-gluster/tree/master/gluster/integration)

from docker-volume-gluster.

It's work fine for me, @sapk Thanks for your help :)

from docker-volume-gluster.

I complete my previous message with the sample code (only work if we use host containers IPs)

Edit: I use @sapk tips for getting IPs

from docker-volume-gluster.

@badele I can recommend you to use docker inspect --format {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}} containerName to get the container IP more reliably.

from docker-volume-gluster.

Does the host have fuse intalled ?

from docker-volume-gluster.

[rancher@rancher ~]$ ls /dev/fuse
/dev/fuse

I have an rclone container that is able to use /dev/fuse to mount a cloud storage drive.

from docker-volume-gluster.

Can you debug the plugin to read the gluster client logs https://docs.docker.com/engine/extend/#debugging-plugins ?
In most case, it should be the host that doesn't resolve one of the name of the gluster hosts.

from docker-volume-gluster.

Hi,

I have a same issue,

I try test you plugin with this docker recipe

Note: the glusterfs cluster it seem work with this recipe

I use a archlinux host, and it seem not log for the docker plugin or i dont't know activate the docker plugin debug/verbose mode (I have actived with docker plugin set sapk/plugin-gluster DEBUG=1 command).

Thank for you help

from docker-volume-gluster.

What an idiot ! i have forgot of replace the hostname by ip for volume creation :)

I think you're right, i will test this this evening

Thank for you help and good job for you project

from docker-volume-gluster.

I did the same ^^ :

from docker-volume-gluster.

from docker-volume-gluster.

If the host can resolve the domains of gluster server it is good.
In the case of @badele it is the container name that he use for gluster server name in volume but those only resolve inside the corresponding docker network.

from docker-volume-gluster.