Re: [Dev] WSO2 Docker images layered composition

On Wed, Jul 6, 2016 at 9:55 AM, Isuru Haththotuwa wrote: > The rationale behind my previous statement is that once the docker images > are pushed to a registry, the users do not have to continuously build them, > but rather can extend from the product Docker images and do

Re: [Dev] WSO2 Docker images layered composition

Hi Imesh, Sorry for the late response. On Tue, Jun 28, 2016 at 9:06 AM, Imesh Gunaratne wrote: > > > On Mon, Jun 27, 2016 at 11:44 PM, Isuru Haththotuwa > wrote: > >> Hi Imesh, >> >> Agreed on the size impact. My concern is that this change does not bring >>

Re: [Dev] WSO2 Docker images layered composition

Hi, > >> Regarding tag names, it was done on purpose do multiple Puppet module >> releases for a specific WSO2 product version. I know it's ugly, but would >> like to hear others' thoughts/suggestions. >> > > ​I'm sorry I do not get this.​ > > ​Can you please explain this in more detail? > I

Re: [Dev] WSO2 Docker images layered composition

On Mon, Jun 27, 2016 at 11:44 PM, Isuru Haththotuwa wrote: > Hi Imesh, > > Agreed on the size impact. My concern is that this change does not bring > in a significant improvement for the model that we have now. > ​I think it has a significant improvement. If we don't use a base

Re: [Dev] WSO2 Docker images layered composition

Hi Akila, On Mon, Jun 27, 2016 at 7:50 PM, Akila Ravihansa Perera wrote: > > Regarding tag names, it was done on purpose do multiple Puppet module > releases for a specific WSO2 product version. I know it's ugly, but would > like to hear others' thoughts/suggestions. > ​I'm

Re: [Dev] WSO2 Docker images layered composition

Hi Imesh, On Thu, Jun 23, 2016 at 3:06 PM, Imesh Gunaratne wrote: > Hi Isuru/Akila, > > On Tue, Jun 21, 2016 at 3:19 PM, Isuru Haththotuwa > wrote: > > To summarize: > >- Publish a wso2 product specific docker image to a local docker >repository (we can

Re: [Dev] WSO2 Docker images layered composition

Hi Ramon, Thanks for sharing this but we will not be able make these official due to OracleJDK license issues. OpenJDK will be fully supported in Carbon 5 based products but that will take some time. Regarding tag names, it was done on purpose do multiple Puppet module releases for a specific

Re: [Dev] WSO2 Docker images layered composition

On Sat, Jun 25, 2016 at 10:21 AM, Akila Ravihansa Perera wrote: > Hi, > > I've merged the PR [1] which introduces wso2base image. This base image > will include packages that were previously installed from Puppet (zip and > unzip), and those are removed from Puppet/Hiera

Re: [Dev] WSO2 Docker images layered composition

Hi, I've merged the PR [1] which introduces wso2base image. This base image will include packages that were previously installed from Puppet (zip and unzip), and those are removed from Puppet/Hiera side. With that we should be able to build WSO2 Docker images in offline mode. wso2base image is

Re: [Dev] WSO2 Docker images layered composition

Hi Isuru/Akila, On Tue, Jun 21, 2016 at 3:19 PM, Isuru Haththotuwa wrote: To summarize: - Publish a wso2 product specific docker image to a local docker repository (we can even push to dockerhub, without the JDK distribution and ask the users to provide the JDK when

Re: [Dev] WSO2 Docker images layered composition

Hi Akila, On Tue, Jun 21, 2016 at 6:54 PM, Akila Ravihansa Perera wrote: > Hi Isuru, > > One drawback of not having a wso2base is that in a restricted environment > where Internet connectivity is not available, a private build server will > not be able to build the images

Re: [Dev] WSO2 Docker images layered composition

Hi Isuru, One drawback of not having a wso2base is that in a restricted environment where Internet connectivity is not available, a private build server will not be able to build the images using Puppet provisioning if there are any additional packages to be installed. But if there was a wso2base

Re: [Dev] WSO2 Docker images layered composition

Hi Isuru, +1 for the suggested approach. I think wso2base image will only complement the model that you have described. We can definitely provide guidelines to users so that they can extend from our product specific images (excluding Oracle JDK). If we have the right layered model, i.e.;

Re: [Dev] WSO2 Docker images layered composition

Hi Akila, If we use a base image, true that we can avoid the time taken to run apt-get update and software installation. But still the users will have to run the provisioning again and again when doing development/testing. The model I suggest is a way to eliminate apt-get update and also the

Re: [Dev] WSO2 Docker images layered composition

Hi Isuru, Do you have any specific concerns about using a wso2base image? On average there is a spike of 100MB when using a wso2base image, but that's a small price to pay when considering benefits users would gain out of this. Note that users can use "default" provisioning method to package any

Re: [Dev] WSO2 Docker images layered composition

Hi Akila and Imesh, Without creating a base image, if we package everything in a product specific image, host it in a local registry, and provide instructions to create a local Dockerfile extending from that image, the time taken to build the local image would be lesser. This will speedup the

Re: [Dev] WSO2 Docker images layered composition

+1 for the idea Akila! I agree with all the points listed above, we experienced those during past couple of weeks after removing the base image. Will include this change in the next Dockerfiles release. Thanks On Mon, May 30, 2016 at 12:48 PM, Akila Ravihansa Perera wrote:

[Dev] WSO2 Docker images layered composition

Hi, Currently we don't have a base image for WSO2 Docker images due to image size issues we had with it. But later we found out that this was mainly due to multiple RUN commands, which caused Docker to add unnecessary layers. I think we should bring back the base image for couple of reasons; 1.