You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2019/09/24 15:27:00 UTC

[jira] [Updated] (BEAM-8293) Document or log file system issues with docker

     [ https://issues.apache.org/jira/browse/BEAM-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía updated BEAM-8293:
-------------------------------
    Status: Open  (was: Triage Needed)

> Document or log file system issues with docker
> ----------------------------------------------
>
>                 Key: BEAM-8293
>                 URL: https://issues.apache.org/jira/browse/BEAM-8293
>             Project: Beam
>          Issue Type: Improvement
>          Components: java-fn-execution
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A frequently asked question about portability in the mailing list is, "Why am I getting IOExceptions in my job?" where the answer is often, because the SDK harness is using docker, which does not have access to the local filesystem by default, so when users try to read/write via transforms or don't set a artifact_staging_location, they get errors. We should at least document this on the website. Even better would be to log something, especially for artifact_staging_location, which is implicit and users might not be aware of.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)