Hi Isuru/Akila,

On Tue, Jun 21, 2016 at 3:19 PM, Isuru Haththotuwa <[email protected]> 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 spinning up a container from the
   image).

A good suggestion, since we currently track product downloads for analytics
we might need to find a way to do the same with Docker if we were to
publicly share WSO2 Docker images. Otherwise using a local registry with a
base/product image would do.

   - Guide the users/developers to create their own Dockerfile extending
   from the original wso2 product Docker image.

We might need to solve 1, to do this.

On Thu, Jun 23, 2016 at 9:42 AM, Isuru Haththotuwa <[email protected]> wrote:

>
> On Tue, Jun 21, 2016 at 6:54 PM, Akila Ravihansa Perera <
> [email protected]> wrote:
>
>>
>> I'm not against having a base image for the WSO2 Docker images. But, IMHO
> the advantages should be significant for doing so. AFAIU there is no
> significant advantage of doing so currently. But, this is my take only.
> Therefore lets get the input from the community on this matter.
>
> @Imesh: WDYT?
>
> ​Currently almost all of us use a base image locally to reduce the
internet bandwidth usage due to executing docker builds from scratch.
Therefore I think it would be better to push that to the remote repository.

As Akila has mentioned the only downside of this is the image size being
increased by around 100 MB. ​When creating Docker images for production
deployment those optimizations can be taken into account.

Thanks

>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>


-- 
*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
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to