Hi Vishanth, The plan is to have the base image in Docker Public registry so that anyone can pull it whenever they want. However, IMO we should also ship the common image artifacts, in case the users need to modify the Base image.
We can additionally link the common Dockerfile with the Docker registry [1]. [1] - https://docs.docker.com/docker-hub/github/ Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Feb 29, 2016 at 12:41 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi, > > This is to discuss the packaging structure of Kubernetes Artifacts. The > project structure is attached [1]. The plan is to package the Docker > related distributions and Kubernetes related distributions separately per > product. > > Docker related distribution of a product would look like this. > <WSO2_PRODUCT>-Docker-1.0.0.zip > |--- <WSO2_PRODUCT>/docker > |--- Common > |------- docker/base-image > |------- scripts/docker > |--- ReadMe.md > > Should we package the docker base-image within every docker distribution > of a product or should it be packaged separately. Thoughts? > > Kubernetes related distribution of a product would look like this. > <WSO2_PRODUCT>-Kubernetes-1.0.0.zip > |--- <WSO2_PRODUCT>/kubernetes > |--- Common > |------- scripts/kubernetes > |--- ReadMe.md > > [1] - Attachment: Kubernetes-Artifacts-Project-Structure.png > > Regards, > Vishanth > > -- > *Vishanth Balasubramaniam* > Committer & PMC Member, Apache Stratos, > Software Engineer, WSO2 Inc.; http://wso2.com > > mobile: *+94 77 17 377 18* > about me: *http://about.me/vishanth <http://about.me/vishanth>* >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
