Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-2661

Docker deploy images should pull upstream images

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Invalid
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.2.0
    • Component/s: deployment
    • Labels:
      None

      Description

      Add --pull to docker build.

      And add ubuntu-16.04, since this is missing

        Activity

        Hide
        oflebbe Olaf Flebbe added a comment -

        Oh you are right. I was using docker-compose. Closing this as invalid.

        Will remove the docker-deploy jobs from CI.

        Show
        oflebbe Olaf Flebbe added a comment - Oh you are right. I was using docker-compose. Closing this as invalid. Will remove the docker-deploy jobs from CI.
        Hide
        evans_ye Evans Ye added a comment -

        Do you need a help? Basically its just simply remove all deploy images and update all the config.yaml to be using bigtop/puppet instead of bigtop/deploy images.

        Show
        evans_ye Evans Ye added a comment - Do you need a help? Basically its just simply remove all deploy images and update all the config.yaml to be using bigtop/puppet instead of bigtop/deploy images.
        Hide
        oflebbe Olaf Flebbe added a comment -

        oops, I forgot about the docker compose thing. Will look into it. Thanks for pointing to it!

        Show
        oflebbe Olaf Flebbe added a comment - oops, I forgot about the docker compose thing. Will look into it. Thanks for pointing to it!
        Hide
        evans_ye Evans Ye added a comment - - edited

        Olaf Flebbe you brought up one of the think I'd like to do but nearly no time to do it.
        Actually we can remove entire deploy series of docker images because now we're running docker natively using docker compose. Hence, ssh daemon and inserting vagrant key would be completed needless.

        We can directly switch the image in provisioner to bigtop/puppet series of images.
        I remember I've done some tests locally and there's no problem I can recall.

        Shall we clean up the deploy directory this time?

        Show
        evans_ye Evans Ye added a comment - - edited Olaf Flebbe you brought up one of the think I'd like to do but nearly no time to do it. Actually we can remove entire deploy series of docker images because now we're running docker natively using docker compose. Hence, ssh daemon and inserting vagrant key would be completed needless. We can directly switch the image in provisioner to bigtop/puppet series of images. I remember I've done some tests locally and there's no problem I can recall. Shall we clean up the deploy directory this time?

          People

          • Assignee:
            oflebbe Olaf Flebbe
            Reporter:
            oflebbe Olaf Flebbe
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development