Subdir is not created and therefore doesn't seem to work, need to create subdir first

[iangregsondev]

Hi,

I wonder if there is a fix coming or could we update the readme about a potential bug?

I had a container setup to work via gluster i.e.

volumes:
  registry_data:
    driver: glusterfs
    name: "gfs/docker-registry"

The container started and everything appeared to be working but the disks were not getting the updates. So i brought down my stack and created the directory manually i.e.

mkdir docker-regsitry

on one of the gluster nodes and now all is working again after brining the stack back up

I see the files appearing on the disk.

Thanks.

[autoize]

Seems like the intended workflow is to manually create the subdirectory (in your case, docker-registry) under the Gluster volume gfs prior to creating the Docker volume. We're trying to get this plugin to work, but are encountering the error in issue #32 . Did you also run into that?

[dazinator]

Have same issue, where I'd like the subdirectory used in the compose file, to be auto created when it doesn't already exist on the gluster volume. Has anyone a compelling solution to this issue that doesn't involve manually creating the folders each time?