Furthermore, the extension management method Raj implement in Puppet modules, where specific extensions were decoupled from the agent module, should also be reflected in the sample Dockerfiles.
IMO a suitable approach for this would be to divide the common Dockerfile instructions from the service specific ones, i.e. have a "base-image" Dockerfile and various "service-image" Dockerfiles for the respective services (php, mysql, tomcat, etc). The base image Dockerfile will contain the agent specific configurations, alone with the agent extensions, and each service image will use the base image as the starting image. They can replace or add custom extensions to the resulting image. I'm in the process of writing a sample set of Dockerfiles, and will give an update soon. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Dec 15, 2014 at 5:54 PM, Chamila De Alwis <chami...@wso2.com> wrote: > > Hi, > > Is there a plan to ship Dockerfiles for the standard set of cartridges in > Stratos? If so, IMO we need to improve the Dockerfile contents of the > sample file we're using[1]. > > A good place to start will be the Dockerfile best practices guide[2] and > this[3] article on avoiding using SSHD in Docker images. The current sample > Dockerfile uses SSHD to ssh into the container and interact with the files. > > [1] - > https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Python+Cartridge+Agent+Guide > > [2] - http://crosbymichael.com/dockerfile-best-practices.html > [3] - http://jpetazzo.github.io/2014/06/23/docker-ssh-considered-evil/ > > > Regards, > Chamila de Alwis > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > >
