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/03/01 17:19:01 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=17293045#comment-17293045 ] 

Beam JIRA Bot commented on BEAM-5440:
-------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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, stale-assigned
>          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)