[
https://issues.apache.org/jira/browse/BEAM-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275456#comment-17275456
]
Kyle Weaver commented on BEAM-5440:
-----------------------------------
Revisiting this. One of the points of contention on
https://github.com/apache/beam/pull/8828 is whether we should put the option in
ManualDockerEnvironmentOptions, or in environmentConfig. Putting it in
ManualDockerEnvironmentOptions is not ideal because it is hidden and has no
equivalent in Python. Whereas putting it in environmentConfig is not possible
without modifying the expected format of the field when environmentType ==
DOCKER, probably by allowing JSON blobs like PROCESS. I think addressing
BEAM-10671 for Java first will help, then we can just add it to the generic
environmentOptions for both Java and Python.
> Add option to mount a directory inside SDK harness containers
> -------------------------------------------------------------
>
> Key: BEAM-5440
> URL: https://issues.apache.org/jira/browse/BEAM-5440
> Project: Beam
> Issue Type: New Feature
> Components: java-fn-execution, sdk-java-core
> Reporter: Maximilian Michels
> Assignee: Kyle Weaver
> Priority: P2
> Labels: Clarified, portability, portability-flink
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
