additional question: As shown below, when I run "gluster peer probe" command on repo-container, the corresponding FAILED occurs. I can referenced the hostname" aio1-repo-container-8ee985f4" from /var/log/glusterfs/cmd_history.log. When referencing this aio1-repo-container-8ee985f4 using the nslookup command "172.29.238.62", and when exiting from the container and referencing the IP address from the host (/etc/hosts), the DNS host names(aio1-unbound-container) do not appear to match. This province seems to have a problem with resolvconf? Anyone know what it is? regards. ---- root@aio1-repo-container-8ee985f4:/# gluster peer probe aio1-repo-container-8ee985f4 peer probe: failed: Probe returned with Transport endpoint is not connected root@aio1-repo-container-8ee985f4:/# root@aio1-repo-container-8ee985f4:/# nslookup aio1_repo_container-8ee985f4 Server: 172.29.238.62 Address: 172.29.238.62#53 ** server can't find aio1_repo_container-8ee985f4: NXDOMAIN root@aio1-repo-container-8ee985f4:/# exit exit # cat /etc/hosts | grep 172.29.238.62 172.29.238.62 aio1-unbound-container-ff4b869c.openstack.local aio1-unbound-container-ff4b869c aio1_unbound_container-ff4b869c