You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/05/15 17:20:02 UTC

[jira] [Updated] (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:all-tabpanel ]

Beam JIRA Bot updated BEAM-5440:
--------------------------------
    Labels: Clarified portability portability-flink stale-P2  (was: Clarified portability portability-flink)

> 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: P2
>              Labels: Clarified, portability, portability-flink, stale-P2
>          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)