@Sajith, Publishing WSO2 products on the Docker official repository will be a process which involves pushing our Dockerfiles to docker-library/official-images [1], and it will involve PRs for them to be updated. IMO this would interfere with our ability to have control over the Dockerfile strategy for WSO2 products. Therefore, I think we should publish (when we do) Docker images under wso2 organization[2].
[1] - https://github.com/docker-library/official-images [2] - https://hub.docker.com/r/wso2/ Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Thu, Mar 31, 2016 at 4:47 PM, Imesh Gunaratne <[email protected]> wrote: > > > On Thu, Mar 31, 2016 at 2:05 PM, Isuru Haththotuwa <[email protected]> > wrote: > >> >> [2]. >> FROM wso2am:1.10.0 >> MAINTAINER [email protected] >> >> COPY artifacts/ /mnt/wso2-artifacts/carbon-home >> > > Shouldn't it better to use a simple folder structure like > "/usr/local/wso2/wso2<product-code>/" instead of above? Apache Httpd [3], > Tomcat [4], JBoss [5] Dockerfiles use something similar. > > [3] > https://github.com/docker-library/httpd/blob/bc72e42914f671e725d85a01ff037ce87c827f46/2.4/Dockerfile#L6 > [3] > https://github.com/docker-library/tomcat/blob/ed98c30c1cd42c53831f64dffa78a0abf7db8e9a/8-jre8/Dockerfile#L3 > [4] https://github.com/jboss-dockerfiles/wildfly/blob/master/Dockerfile#L7 > > Thanks > > >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> > > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.io > Lean . Enterprise . Middleware > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
