You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2022/05/04 01:07:00 UTC
[jira] [Commented] (BEAM-5440) Add option to mount a directory inside SDK harness containers
[ https://issues.apache.org/jira/browse/BEAM-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531467#comment-17531467 ]
Kyle Weaver commented on BEAM-5440:
-----------------------------------
[~altay] I don't think Dataflow is in scope for this FR. Specifically we are targeting local portable runners so users can test their containers before running on Dataflow, such as the instructions here: https://cloud.google.com/dataflow/docs/guides/using-custom-containers#basic_testing_with_portablerunner
> 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
> Priority: P3
> 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.20.7#820007)