I also have noted that earlier, even when I tested with a private docker registry, but couldn't investigate much on that yet. Seems those are reported as issues and have fixed, may be available with the latest version. [1] [2]
Yeah, better to verify from the group [1] https://github.com/GoogleCloudPlatform/kubernetes/issues/504 [2] https://github.com/GoogleCloudPlatform/kubernetes/issues/1293 On Wed, Oct 22, 2014 at 9:47 AM, Nirmal Fernando <[email protected]> wrote: > Hi Chamila, > > We need to talk to Kubernetes team and understand the exact behavior. > Please have a chat with them at the #google-containers IRC channel. > > On Wed, Oct 22, 2014 at 12:11 AM, Chamila De Alwis <[email protected]> > wrote: > >> Hi, >> >> I'm not sure if this was discussed earlier, and if it was please direct >> me to the thread title. >> >> In the Kubernetes setup, it seems if the mentioned image is present in a >> Docker repository, the central Docker hub in the normal case, Docker will >> pull that image and replace over the image already loaded in to the >> container host instead of using the loaded image. So this means the image >> in the repository has priority over the locally loaded image. >> >> Shouldn't it be the other way around? >> >> Regards, >> Chamila de Alwis >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ > -- *Sajith Kariyawasam* *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
