Uploaded image for project: 'Hadoop Distributed Data Store'
  1. Hadoop Distributed Data Store
  2. HDDS-1523 Ozone Docker container phase 1
  3. HDDS-1495

Create hadoop/ozone docker images with inline build process

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Target Version/s:

      Description

      This is proposed by Eric Yang in this mailing thread.

      1, 3. There are 38 Apache projects hosting docker images on Docker hub using Apache Organization. By browsing Apache github mirror. There are only 7 projects using a separate repository for docker image build. Popular projects official images are not from Apache organization, such as zookeeper, tomcat, httpd. We may not disrupt what other Apache projects are doing, but it looks like inline build process is widely employed by majority of projects such as Nifi, Brooklyn, thrift, karaf, syncope and others. The situation seems a bit chaotic for Apache as a whole. However, Hadoop community can decide what is best for Hadoop. My preference is to remove ozone from source tree naming, if Ozone is intended to be subproject of Hadoop for long period of time. This enables Hadoop community to host docker images for various subproject without having to check out several source tree to trigger a grand build. However, inline build process seems more popular than separated process. Hence, I highly recommend making docker build inline if possible.

      The main challenges are also discussed in the thread:

      3. Technically it would be possible to add the Dockerfile to the source
      tree and publish the docker image together with the release by the
      release manager but it's also problematic:
      
      

      a) there is no easy way to stage the images for the vote
      c) it couldn't be flagged as automated on dockerhub
      d) It couldn't support the critical updates.

      • Updating existing images (for example in case of an ssl bug, rebuild
        all the existing images with exactly the same payload but updated base
        image/os environment)
      • Creating image for older releases (We would like to provide images,
        for hadoop 2.6/2.7/2.7/2.8/2.9. Especially for doing automatic testing
        with different versions).
       

      The a) can be solved (as Eric Yang suggested) with using a personal docker image during the vote and publish it to the dockerhub after the vote (in case the permission can be set by the INFRA)

      Note: based on LEGAL-270 and linked discussion both approaches (inline build process / external build process) are compatible with the apache release.

      Note: HDDS-851 and HADOOP-14898 contains more information about these problems.

        Attachments

        1. HDDS-1495.008.patch
          31 kB
          Eric Yang
        2. Hadoop Docker Image inline build process.pdf
          115 kB
          Eric Yang
        3. HDDS-1495.007.patch
          33 kB
          Eric Yang
        4. HDDS-1495.006.patch
          18 kB
          Eric Yang
        5. HDDS-1495.005.patch
          14 kB
          Eric Yang
        6. HDDS-1495.004.patch
          13 kB
          Eric Yang
        7. HDDS-1495.003.patch
          13 kB
          Eric Yang
        8. HADOOP-16091.002.patch
          12 kB
          Eric Yang
        9. HADOOP-16091.001.patch
          12 kB
          Eric Yang

          Activity

            People

            • Assignee:
              eyang Eric Yang
              Reporter:
              elek Elek, Marton
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: