+1 I think it's a great idea to make Docker images available.
Not sure it makes sense to package client(s) as images, but overall I think the idea would help make Qpid more easily accessible to users and help ease deployment. -Steve > -----Original Message----- > From: Irina Boverman [mailto:[email protected]] > Sent: Tuesday, June 13, 2017 10:13 AM > To: qpid <[email protected]> > Subject: Proposal to create Docker images for Qpid components. > > Hi everyone, > > I would like to propose creating Docker images for Qpid components hosted > in Docker Hub, updated upon component release and maintained by the > project, and I would like to contribute to doing this. > > Availability of Qpid images will make it easier to consume/deploy Qpid > components and promote Qpid visibility. > > We can maintain docker scripts creating these images from the base OS > images and using Qpid installation methods consistent with the OS > distribution. A possible naming convention might be > qpid/<component>/<OS>. > I registered the 'qpid' user on DockerHub to use if this seems reasonable. > For example, we could create qpid/dispatch/<OS> image, > qpid/<broker>/<OS> image, qpid/<client(s)>/<OS> image, etc. Initially I > would look to support Fedora/CentOS latest images and Qpid components as > RPMs for them, then aim to expand OS coverage for debian/Ubuntu/etc in > the future. > > The goal would be to update Qpid images within a few days upon component > release (either directly or indirectly using yum/dnf from public > repositories). > We could ask the Docker team to grant Qpid "official" status when images > have been stabilized. > -- > Regards, Irina.
