You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried the current master branch (aeecbb6) on a simple Docker host with GlusterFS 4.1. It appears to be working EXCEPT when a non-existent subdirectory is specified. Did something change between GlusterFS 3.x and 4.1?
Volume persistence WORKS with a bare Gluster volume:
docker run -it --rm --volume-driver gluster1 -v gfs1:/data alpine
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
srv1:gfs1 14624768 2320512 12304256 16% /data
Using a subdir is SILENTLY BROKEN - all appears well until the container terminates and your "persistent" data is vaporized:
docker run -it --rm --volume-driver gluster1 -v gfs1/dir1:/data alpine
Evidence of a problem can be seen in "df" output: it returns an unexpected device (the filesystem of /var/lib/docker) instead of the GlusterFS device:
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg1-lv_docker
314394636 403180 313991456 0% /data
Specifying a subdir WORKS if it has already been created within the GlusterFS volume:
docker run -it --rm --volume-driver gluster1 -v gfs1/n:/data alpine
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
srv1:gfs1/n 14624768 2320512 12304256 16% /data
Install/version info
For this testing, the Docker host served as one of the two peers in the GlusterFS cluster.
I tried the current master branch (aeecbb6) on a simple Docker host with GlusterFS 4.1. It appears to be working EXCEPT when a non-existent subdirectory is specified. Did something change between GlusterFS 3.x and 4.1?
Volume persistence WORKS with a bare Gluster volume:
Using a subdir is SILENTLY BROKEN - all appears well until the container terminates and your "persistent" data is vaporized:
Evidence of a problem can be seen in "df" output: it returns an unexpected device (the filesystem of /var/lib/docker) instead of the GlusterFS device:
Specifying a subdir WORKS if it has already been created within the GlusterFS volume:
Install/version info
For this testing, the Docker host served as one of the two peers in the GlusterFS cluster.
The text was updated successfully, but these errors were encountered: