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 <bpar...@redhat.com> wrote:

>
>
> On Wed, Jul 27, 2016 at 1:23 PM, Akshaya Khare <khare...@husky.neu.edu>
> 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 inspect the pod definition to confirm what image the container is
> running?  And can you oc rsh into the running container and poke around to
> see if your changes are present?
>
> have you confirmed if you "docker run localhost:5000/jenkins-bmi3 /bin/sh"
> that it contains your changes?
>
> Also i'm assuming you only have a single node and it's the same machine as
> "localhost", otherwise it's not clear how the image is going to get pulled
> to the node that's running the pod.
> ​
>
>
>>
>>
>> On Wed, Jul 27, 2016 at 1:20 PM, Ben Parees <bpar...@redhat.com> wrote:
>>
>>>
>>>
>>> On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare <khare...@husky.neu.edu>
>>> 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 new app
>>>> using the below command, and a pod got deployed shortly after the app was
>>>> created
>>>>
>>>> *# oc new-app -e JENKINS_PASSWORD=<mypassword>
>>>> localhost:5000/jenkins-bmi2*
>>>>
>>>
>>> ​you pushed it to bmi3 and deployed bmi-2?
>>> ​
>>>
>>>
>>>>
>>>>
>>>> Thats all I did...
>>>> As per your advice, I'll try using s2i for extending an image, and
>>>> thanks for replying so quickly...
>>>>
>>>> Regards,
>>>> AK
>>>>
>>>> On Wed, Jul 27, 2016 at 12:37 PM, Ben Parees <bpar...@redhat.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare <
>>>>> khare...@husky.neu.edu> 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 Source-To-Image builder
>>>>>>
>>>>>> Now i found docker layering to be ideal in my case since I have
>>>>>> created a new project and made many configurations to make it work.
>>>>>>
>>>>>> I ran the below command for getting the new image
>>>>>>
>>>>>> *# docker commit -m "my message" <containerid> <new image name:tag>*
>>>>>>
>>>>>
>>>>> ​first of all i'd strongly discourage you from creating images in this
>>>>> way since you don't have a recreatable pattern.  you should definitely
>>>>> create a dockerfile if you're going to extend an image (or use s2i).
>>>>> ​
>>>>>
>>>>>
>>>>>> I pushed it to my local registry and used it to create a new
>>>>>> application in openshift.
>>>>>>
>>>>>
>>>>> ​what did you tag it as an how did you create the new application?
>>>>> ​
>>>>>
>>>>>
>>>>>> It did get deployed, but the jenkins image doesn't contain any of my
>>>>>> changes...
>>>>>>
>>>>>
>>>>> ​how did you deploy the new image?​
>>>>>
>>>>>
>>>>>> comparing the history of both the original image and the modified
>>>>>> image, it looks like it did add a new layer:
>>>>>>
>>>>>>
>>>>>>
>>>>>> *IMAGE                  CREATED             CREATED
>>>>>> BY                                                  SIZE
>>>>>> COMMENTe99517b97a3e        21 hours ago
>>>>>> /usr/libexec/s2i/run                                         1.886
>>>>>> MB            jenkins 3rd attemptc014669e27a0        11 days ago
>>>>>> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B                 *
>>>>>>
>>>>>> So finally coming to my question, am I missing something while
>>>>>> creating a new docker layer for my jenkins image?
>>>>>>
>>>>>
>>>>> ​i'm guessing you just didn't actually deploy your new image, but
>>>>> we'll need some more details about your steps to know for sure.
>>>>> ​
>>>>>
>>>>>
>>>>>> Or should i just use Source to image builder for my changes?
>>>>>>
>>>>>>
>>>>>> Thanks & Regards,
>>>>>>
>>>>>> AK
>>>>>>
>>>>>> _______________________________________________
>>>>>> users mailing list
>>>>>> users@lists.openshift.redhat.com
>>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ben Parees | OpenShift
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Thanks & Regards,*
>>>> *Akshaya Khare*
>>>> *312-785-3508 <312-785-3508>*
>>>>
>>>
>>>
>>>
>>> --
>>> Ben Parees | OpenShift
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,*
>> *Akshaya Khare*
>> *312-785-3508 <312-785-3508>*
>>
>
>
>
> --
> Ben Parees | OpenShift
>
>


-- 
*Thanks & Regards,*
*Akshaya Khare*
*312-785-3508*
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to