[BEAM-5440] Add option to mount a directory inside SDK harness containers

• Type: New Feature
• Status: Triage Needed
• Priority: P3
• Resolution: Unresolved
• Component/s: java-fn-execution, sdk-java-core
• Labels: Clarified portability portability-flink
• Assignee: Unassigned
• Reporter: Maximilian Michels
• Created: 20/Sep/18 13:30
• Updated: 15/May/23 18:44

Description

While experimenting with the Python SDK locally, I found it inconvenient that I can't mount a host directory to the Docker containers, i.e. the input must already be in the container and the results of a Write remain inside the container. For local testing, users may want to mount a host directory.

Since BEAM-5288 the Environment carries explicit environment information, we could a) add volume args to the DockerPayload, or b) provide a general Docker arguments field.

Issue Links

• Dependency: BEAM-5288 Modify Environment to support non-dockerized SDK harness deployments
• is duplicated by: BEAM-8239 Docker options in --environment_config
• is duplicated by: BEAM-5273 Local file system does not work as expected on Portability Framework with Docker
• is duplicated by: BEAM-6891 Support extra mount volumes for PortableRunner's docker container
• is duplicated by: BEAM-7534 add --mountTempDir option for easier data sharing with Docker container
• links to: GitHub Pull Request #8982