From fc0a0a8d31e431e889c4bb46930749f632a2002c Mon Sep 17 00:00:00 2001 From: David Young Date: Wed, 3 Jun 2020 15:43:56 +1200 Subject: [PATCH] Fix el glustetr --- manuscript/ha-docker-swarm/shared-storage-gluster.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manuscript/ha-docker-swarm/shared-storage-gluster.md b/manuscript/ha-docker-swarm/shared-storage-gluster.md index 6aa80e2..a4c9e32 100644 --- a/manuscript/ha-docker-swarm/shared-storage-gluster.md +++ b/manuscript/ha-docker-swarm/shared-storage-gluster.md @@ -78,8 +78,7 @@ docker run \ On a single node (doesn't matter which), run ```docker exec -it glusterfs-server bash``` to launch a shell inside the container. -From the node, run -```gluster peer probe ``` +From the node, run `gluster peer probe `. Example output: @@ -138,6 +137,7 @@ From one other host, run ```docker exec -it glusterfs-server bash``` to shell in ### Mount gluster volume On the host (i.e., outside of the container - type ```exit``` if you're still shelled in), create a mountpoint for the data, by running ```mkdir /var/data```, add an entry to fstab to ensure the volume is auto-mounted on boot, and ensure the volume is actually _mounted_ if there's a network / boot delay getting access to the gluster volume: + ``` mkdir /var/data MYHOST=`hostname -s`