OpenShift runs same container twice when it should run two different ones inside pod












0














I want OpenShift 3.10 to create a pod (console) comprising two containers (api and console). The relevant description in the application template (under dc.spec.template.spec.containers) for DeploymentConfig console looks like this:



containers:
- image: console:api
imagePullPolicy: Always
name: api
terminationMessagePolicy: File
- image: console:console
imagePullPolicy: Always
name: console
ports:
- containerPort: 80
protocol: TCP
terminationMessagePolicy: File


oc describe is/console looks good to me and reports the following (the BuildConfigs for the two containers output to ImageStreamTags console:api and console:console respectively):



api
no spec tag
* docker-registry.default.svc:5000/registry/console@sha256:96...66
console
no spec tag
* docker-registry.default.svc:5000/registry/console@sha256:8a...02


But oc describe pods --selector deploymentconfig=console reveals that the same image has been pulled twice and hence the same container runs twice inside the pod:



Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"
Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"


How can I ensure that the pod indeed comprises the two distinct containers? And why is the image stream tag console:api apparently at times not referring to image 96...66 but also to 8a...02, contrary to what os describe is/console suggests?



UPDATE The mismatch is also apparent in oc describe dc/console, which indicates that both image stream tags console:api and console:console apparently have been resolved to the same container image 8a...02:



Containers:
api:
Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02
console:
Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02









share|improve this question





























    0














    I want OpenShift 3.10 to create a pod (console) comprising two containers (api and console). The relevant description in the application template (under dc.spec.template.spec.containers) for DeploymentConfig console looks like this:



    containers:
    - image: console:api
    imagePullPolicy: Always
    name: api
    terminationMessagePolicy: File
    - image: console:console
    imagePullPolicy: Always
    name: console
    ports:
    - containerPort: 80
    protocol: TCP
    terminationMessagePolicy: File


    oc describe is/console looks good to me and reports the following (the BuildConfigs for the two containers output to ImageStreamTags console:api and console:console respectively):



    api
    no spec tag
    * docker-registry.default.svc:5000/registry/console@sha256:96...66
    console
    no spec tag
    * docker-registry.default.svc:5000/registry/console@sha256:8a...02


    But oc describe pods --selector deploymentconfig=console reveals that the same image has been pulled twice and hence the same container runs twice inside the pod:



    Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"
    Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"


    How can I ensure that the pod indeed comprises the two distinct containers? And why is the image stream tag console:api apparently at times not referring to image 96...66 but also to 8a...02, contrary to what os describe is/console suggests?



    UPDATE The mismatch is also apparent in oc describe dc/console, which indicates that both image stream tags console:api and console:console apparently have been resolved to the same container image 8a...02:



    Containers:
    api:
    Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02
    console:
    Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02









    share|improve this question



























      0












      0








      0







      I want OpenShift 3.10 to create a pod (console) comprising two containers (api and console). The relevant description in the application template (under dc.spec.template.spec.containers) for DeploymentConfig console looks like this:



      containers:
      - image: console:api
      imagePullPolicy: Always
      name: api
      terminationMessagePolicy: File
      - image: console:console
      imagePullPolicy: Always
      name: console
      ports:
      - containerPort: 80
      protocol: TCP
      terminationMessagePolicy: File


      oc describe is/console looks good to me and reports the following (the BuildConfigs for the two containers output to ImageStreamTags console:api and console:console respectively):



      api
      no spec tag
      * docker-registry.default.svc:5000/registry/console@sha256:96...66
      console
      no spec tag
      * docker-registry.default.svc:5000/registry/console@sha256:8a...02


      But oc describe pods --selector deploymentconfig=console reveals that the same image has been pulled twice and hence the same container runs twice inside the pod:



      Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"
      Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"


      How can I ensure that the pod indeed comprises the two distinct containers? And why is the image stream tag console:api apparently at times not referring to image 96...66 but also to 8a...02, contrary to what os describe is/console suggests?



      UPDATE The mismatch is also apparent in oc describe dc/console, which indicates that both image stream tags console:api and console:console apparently have been resolved to the same container image 8a...02:



      Containers:
      api:
      Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02
      console:
      Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02









      share|improve this question















      I want OpenShift 3.10 to create a pod (console) comprising two containers (api and console). The relevant description in the application template (under dc.spec.template.spec.containers) for DeploymentConfig console looks like this:



      containers:
      - image: console:api
      imagePullPolicy: Always
      name: api
      terminationMessagePolicy: File
      - image: console:console
      imagePullPolicy: Always
      name: console
      ports:
      - containerPort: 80
      protocol: TCP
      terminationMessagePolicy: File


      oc describe is/console looks good to me and reports the following (the BuildConfigs for the two containers output to ImageStreamTags console:api and console:console respectively):



      api
      no spec tag
      * docker-registry.default.svc:5000/registry/console@sha256:96...66
      console
      no spec tag
      * docker-registry.default.svc:5000/registry/console@sha256:8a...02


      But oc describe pods --selector deploymentconfig=console reveals that the same image has been pulled twice and hence the same container runs twice inside the pod:



      Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"
      Successfully pulled image "docker-registry.default.svc:5000/registry/console@sha256:8a...02"


      How can I ensure that the pod indeed comprises the two distinct containers? And why is the image stream tag console:api apparently at times not referring to image 96...66 but also to 8a...02, contrary to what os describe is/console suggests?



      UPDATE The mismatch is also apparent in oc describe dc/console, which indicates that both image stream tags console:api and console:console apparently have been resolved to the same container image 8a...02:



      Containers:
      api:
      Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02
      console:
      Image: docker-registry.default.svc:5000/registry/console@sha256:8a...02






      openshift






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 at 23:06

























      asked Nov 22 at 16:01









      rookie099

      35010




      35010
























          1 Answer
          1






          active

          oldest

          votes


















          1














          The following change to dc.spec.triggers seems to have resolved the situation:



          - type: ConfigChange
          - imageChangeParams:
          automatic: true
          containerNames:
          - api
          from:
          kind: ImageStreamTag
          name: console:api
          namespace: registry
          type: ImageChange
          - imageChangeParams:
          automatic: true
          containerNames:
          - console
          from:
          kind: ImageStreamTag
          name: console:console
          namespace: registry
          type: ImageChange


          Previously, there was only a single imageChangeParams for console:console. The pod now comprises the two distinct containers.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434624%2fopenshift-runs-same-container-twice-when-it-should-run-two-different-ones-inside%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            The following change to dc.spec.triggers seems to have resolved the situation:



            - type: ConfigChange
            - imageChangeParams:
            automatic: true
            containerNames:
            - api
            from:
            kind: ImageStreamTag
            name: console:api
            namespace: registry
            type: ImageChange
            - imageChangeParams:
            automatic: true
            containerNames:
            - console
            from:
            kind: ImageStreamTag
            name: console:console
            namespace: registry
            type: ImageChange


            Previously, there was only a single imageChangeParams for console:console. The pod now comprises the two distinct containers.






            share|improve this answer


























              1














              The following change to dc.spec.triggers seems to have resolved the situation:



              - type: ConfigChange
              - imageChangeParams:
              automatic: true
              containerNames:
              - api
              from:
              kind: ImageStreamTag
              name: console:api
              namespace: registry
              type: ImageChange
              - imageChangeParams:
              automatic: true
              containerNames:
              - console
              from:
              kind: ImageStreamTag
              name: console:console
              namespace: registry
              type: ImageChange


              Previously, there was only a single imageChangeParams for console:console. The pod now comprises the two distinct containers.






              share|improve this answer
























                1












                1








                1






                The following change to dc.spec.triggers seems to have resolved the situation:



                - type: ConfigChange
                - imageChangeParams:
                automatic: true
                containerNames:
                - api
                from:
                kind: ImageStreamTag
                name: console:api
                namespace: registry
                type: ImageChange
                - imageChangeParams:
                automatic: true
                containerNames:
                - console
                from:
                kind: ImageStreamTag
                name: console:console
                namespace: registry
                type: ImageChange


                Previously, there was only a single imageChangeParams for console:console. The pod now comprises the two distinct containers.






                share|improve this answer












                The following change to dc.spec.triggers seems to have resolved the situation:



                - type: ConfigChange
                - imageChangeParams:
                automatic: true
                containerNames:
                - api
                from:
                kind: ImageStreamTag
                name: console:api
                namespace: registry
                type: ImageChange
                - imageChangeParams:
                automatic: true
                containerNames:
                - console
                from:
                kind: ImageStreamTag
                name: console:console
                namespace: registry
                type: ImageChange


                Previously, there was only a single imageChangeParams for console:console. The pod now comprises the two distinct containers.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 23:24









                rookie099

                35010




                35010






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434624%2fopenshift-runs-same-container-twice-when-it-should-run-two-different-ones-inside%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Berounka

                    Sphinx de Gizeh

                    Different font size/position of beamer's navigation symbols template's content depending on regular/plain...