Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-2875

Portable SDK harness containers

Details

    • Improvement
    • Status: Resolved
    • P2
    • Resolution: Fixed
    • None
    • 2.3.0
    • beam-model

    Description

      To allow runners to handle current and future SDK harnesses uniformly, each SDK harness must be packaged as a docker container image satisfying the contact proposed here:

      https://s.apache.org/beam-fn-api-container-contract

      The suggested structure is to use a Dockerfile with all dependencies (JRE, python 2.7, etc) and a separate minimal "boot" program in Go that retrieves staged files and invokes the SDK-specific harness. This structure allows flexibility to set up the environment dynamically as well as code sharing across SDKs.

      Attachments

        Issue Links

          Activity

            People

              herohde Henning Rohde
              herohde Henning Rohde
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: