On Mon, 2017-06-19 at 13:16 +0100, Robbie Gemmell wrote: > - To the comments around the Java broker, I don't think creating > packages for it is really necessary? From a quick look at some others > images it doesnt seem unusual to have a Dockerfile set up to pull the > existing binary release archive, verify its sigs, and > extract+configure it in an appropriate location. >
Great. That would work for me. I just thought it would be good to have the entire Qpid project represented and to provide some choice at the same time. Kind regards, Lorenz > Robbie > > On 13 June 2017 at 15:13, Irina Boverman <[email protected]> wrote: > > > > 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. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
