Hi Niels, Built GlusterFS image from Dockerfile: # docker images REPOSITORY TAG IMAGE ID CREATED SIZE dockerfile-gluster-3.12 latest 4647c9d71843 53 minutes ago 371.2 MB docker.io/centos 7 ff426288ea90 5 weeks ago 207.2 MB # docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9afa8c0ab468 dockerfile-gluster-3.12 "/usr/sbin/init" 38 minutes ago Up 38 minutes small_shannon # docker exec -it 9afa8c0ab468 bash # glusterd -V glusterfs 3.12.5 Repository revision: git://git.gluster.org/glusterfs.git Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/> GlusterFS comes with ABSOLUTELY NO WARRANTY. It is licensed to you under your choice of the GNU Lesser General Public License, version 3 or any later version (LGPLv3 or later), or the GNU General Public License, version 2 (GPLv2), in all cases as published by the Free Software Foundation. Updated the Dockerfile and changed Gluster version and vendor, a pull request has been sent on Github. Regards, Javier Romero E-mail: xavinux at gmail.com Skype: xavinux 2018-02-14 9:51 GMT-03:00 Javier Romero <xavinux at gmail.com>: > Niels, > > Thanks for your answer. I'll be looking at the container you have > suggested and will let you know how things are going. > > Regards, > Javier Romero > E-mail: xavinux at gmail.com > Skype: xavinux > > > > 2018-02-14 6:48 GMT-03:00 Niels de Vos <ndevos at redhat.com>: >> On Tue, Feb 13, 2018 at 09:55:02PM -0300, Javier Romero wrote: >>> 2018-02-13 13:07 GMT-03:00 Niels de Vos <ndevos at redhat.com>: >>> >>> > On Mon, Feb 12, 2018 at 07:32:40PM -0300, Javier Romero wrote: >> ... >>> > > Have also been working with KVM virtual machines in the ISP Datacenter >>> > > for the last eight years, and with Docker since 2015, so think that >>> > > can also help with container and VM images if this can be useful. >>> > >>> > We do have a Gluster container in the CentOS Container Index [3], but >>> > would like to have different versions. At the moment, we actively >>> > maintain Gluster versions 3.10, 3.12, 3.13 and are preparing for 4.0. >>> > Ideally we should have a container for each version. >>> > >>> > For which version of Gluster would you like me to start creating a >>> container image first? >> >> Have a look at >> https://github.com/gluster/gluster-containers/tree/master/CentOS. This >> is the container that is currently built for the CentOS Registry and >> available at >> https://registry.centos.org/repo/gluster/storagesig-gluster-centos. >> >> This container seems incorrect as well, the centos-release-gluster >> package will install the latest Long-Term-Maintenance version, currently >> 3.12, but the version mentioned in the container is 3.10. In addition to >> that, the Vendor should either be CentOS or Gluster Community. There >> might be more things that can be improved. >> >> I suggest to have a go at making sure the current container is correct. >> Once done, add a container for 3.10 (by installing >> centos-release-gluster-310). Maybe place the Dockerfile in a different >> directory, or just name it Dockerfile.3.10 or such. After that is >> merged, it can be added to >> https://github.com/CentOS/container-index/blob/master/index.d/gluster.yml >> >> Both Humble and Jose have been looking at the container images before. >> They are on CC of this email and can help with any PullRequest reviews >> or further guidance. >> >> Thanks! >> Niels >> >> >> ... >>> > 0. http://lists.gluster.org/mailman/listinfo/packaging >>> > 1. https://github.com/CentOS-Storage-SIG >>> > 2. https://github.com/CentOS-Storage-SIG/glusterfs >>> > 3. https://github.com/CentOS/container-index >>> > 4. https://app.vagrantup.com/centos >>> >