fstype should be glusterfs

[guidtz]

Hello

Describe the bug When I try to deploy a container with glusterfs drivers :

# docker run -it --rm --volume-driver glusterfs -v swarm-glust-vol1/dir1:/data alpine
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/594396d66d9a36561f8c81cdc1e0ffe260b1d868311760852e8d36cb7cd3f6ba/rootfs': VolumeDriver.Mount: error mounting swarm-glust-vol1/dir1:
Type
ext4

fstype should be glusterfs.

Server (please complete the following information):

• OS: Debian 10
• Docker : Docker version 20.10.7
• glusterfs-common 5.5-3
• swarm initialised

# gluster volume info
 
Volume Name: swarm-glust-vol1
Type: Replicate
Volume ID: 05e14e69-3a9d-4245-bd3d-a776482a46aa
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 5 = 5
Transport-type: tcp
Bricks:
Brick1: swarm-man01:/gluster/volume1/data
Brick2: swarm-man02:/gluster/volume1/data
Brick3: swarm-wk01:/gluster/volume1/data
Brick4: swarm-wk02:/gluster/volume1/data
Brick5: swarm-wk03:/gluster/volume1/data
Options Reconfigured:
auth.allow: docker-compose.yml
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off

Glusterfs works fine

Thanks

[am97]

I got a similar issue. My workaround was to create manually the subdir (dir1 in your case) in my gluster volume.

[johny-mnemonic]

Similar error is generated also from S3fs plugin. Seems like fstype should be glusterfs/s3fs means that the plugin failed to mount the volume. With s3fs it also fails to create the bucket, but even when you create the bucket manually you can get this error when the fs options are incorrect...

[SamB-GB]

I got a similar issue. My workaround was to create manually the subdir (dir1 in your case) in my gluster volume.

Saw the same issue and this fixed it for me too.