Re: Docker layering for jenkins image issue

ok, the changes are not present in the running container. And yes the pod is working on the latest image, which means my image is somehow not updated... So I guess I should create a new image using s2i and then try again? On Wed, Jul 27, 2016 at 1:26 PM, Ben Parees wrote: >

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 1:36 PM, Akshaya Khare wrote: > ok, the changes are not present in the running container. > And yes the pod is working on the latest image, which means my image is > somehow not updated... > > So I guess I should create a new image using s2i and

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 1:23 PM, Akshaya Khare wrote: > sorry, that was an old command, I ran this command > > *oc new-app -e JENKINS_PASSWORD=password localhost:5000/jenkins-bmi3* > ​ok, i'd certainly expect that to result in a pod running your new image. Can you

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare wrote: > Hi Ben, > > Using the below commands I pushed it to my local docker registry: > > > > *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker > push localhost:5000/jenkins-bmi3:latest*Then I created a

Re: Docker layering for jenkins image issue

Hi Ben, Using the below commands I pushed it to my local docker registry: *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker push localhost:5000/jenkins-bmi3:latest*Then I created a new app using the below command, and a pod got deployed shortly after the app was created

Re: Docker layering for jenkins image issue

On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare wrote: > Hi > > While going through the documentation for using *jenkins* image, I found > that we can use the updated image of jenkins by: > >- > >Use Docker layering. >- > >Use the image as a

Docker layering for jenkins image issue

Hi While going through the documentation for using *jenkins* image, I found that we can use the updated image of jenkins by: - Use Docker layering. - Use the image as a Source-To-Image builder Now i found docker layering to be ideal in my case since I have created a new project