[
https://issues.apache.org/jira/browse/BEAM-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated BEAM-5440:
-------------------------------------
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 the {{Environment}} now carries explicit environment information, we
could a) add volume args to the {{DockerPayload}}, or b) provide a general
Docker arguments field.
was:
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 results of a
Write inside a container remain in the container. For local testing, users may
want to mount a host directory.
Since the {{Environment}} now carries explicit environment information, we
could a) add volume args to the {{DockerPayload}}, or b) provide a general
Docker arguments field.
> 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
> Reporter: Maximilian Michels
> Priority: Major
> Fix For: 2.8.0
>
>
> 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 the {{Environment}} now 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
(v7.6.3#76005)
