[BEAM-2875] Portable SDK harness containers

• Type: Improvement
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.3.0
• Component/s: beam-model
• Labels: portability
• Assignee: Henning Rohde
• Reporter: Henning Rohde
• Created: 11/Sep/17 16:07
• Updated: 16/May/20 13:42
• Resolved: 10/Oct/17 22:19

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.

Issue Links

• is depended upon by: BEAM-2878 Release process for container images