Hi Akila, What you are saying is correct. We will use apt-get install in SVN docker image and get rid of base image. And also I will use the image name as wso2/svn:1.0.0 as we can push this to docker hub.
Thank you! On Thu, Jul 21, 2016 at 10:59 AM, Akila Ravihansa Perera <[email protected] > wrote: > Hi Pubudu, > > True, but this image will not be built regularly right? Once we push to > DockerHub users can pull instead of building? > > Thanks. > > > On Thursday, 21 July 2016, Imesh Gunaratne <[email protected]> wrote: > >> >> >> On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka <[email protected]> >> wrote: >> >>> Hi Akila, >>> >>> I used the base image to get rid of running apt-get update again for svn >>> docker image. Apt-get update takes time and also sometimes it fails as >>> well. >>> >>> I have already created Mesos artifacts for svn in [1] and will push >>> those changes to Mesos artifact repo. Will work on the Kubernetes artifacts. >>> >> >> May be we can first focus on Mesos artifacts. Will add this to K8S >> artifacts later on. Might be better to track it in JIRA. >> >> Thanks >> >> >>> >>> [1] - >>> https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn >>> >>> Thank you! >>> >>> On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera < >>> [email protected]> wrote: >>> >>>> Hi Pubudu, >>>> >>>> Why are we using wso2/wso2base:latest as the base image here? We have >>>> to run apt-get update and install subversion anyway right? >>>> >>>> IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes >>>> etc. and integrate this with WSO2 DepSync. Shall we work on delivering the >>>> complete package as well? >>>> >>>> Thanks. >>>> >>>> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka <[email protected]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> At the moment there is no any official docker image for SVN[1]. I have >>>>> created the dockerfile and other relevant artifacts for SVN [2]. This is >>>>> to >>>>> maintain a separate a docker image for SVN for deployment synchronization. >>>>> For dep sync in container deployments, there is a mail thread with subject >>>>> in [3]. >>>>> >>>>> Basically rsync is an option for dep sync. But when it compares to >>>>> SVN, the following are the main advantages. >>>>> >>>>> - Can handle several manager nodes >>>>> - SVN Container can accommodate multiple products >>>>> - We can mount a single volume for SVN server only >>>>> >>>>> Please share your thoughts. >>>>> >>>>> [1] - https://hub.docker.com/ >>>>> [2] - https://github.com/wso2/dockerfiles/pull/57 >>>>> [3] - [Architecture] Dep sync strategies for Carbon 4 products in >>>>> Kubernetes >>>>> >>>>> Thank you! >>>>> -- >>>>> *Pubudu Gunatilaka* >>>>> Committer and PMC Member - Apache Stratos >>>>> Software Engineer >>>>> WSO2, Inc.: http://wso2.com >>>>> mobile : +94774078049 <%2B94772207163> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Akila Ravihansa Perera >>>> WSO2 Inc.; http://wso2.com/ >>>> >>>> Blog: http://ravihansa3000.blogspot.com >>>> >>> >>> >>> >>> -- >>> *Pubudu Gunatilaka* >>> Committer and PMC Member - Apache Stratos >>> Software Engineer >>> WSO2, Inc.: http://wso2.com >>> mobile : +94774078049 <%2B94772207163> >>> >>> >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
