[
https://issues.apache.org/jira/browse/BEAM-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Weaver resolved BEAM-8164.
-------------------------------
Fix Version/s: Not applicable
Resolution: Fixed
> Correct document for building the python SDK harness container
> --------------------------------------------------------------
>
> Key: BEAM-8164
> URL: https://issues.apache.org/jira/browse/BEAM-8164
> Project: Beam
> Issue Type: Bug
> Components: website
> Reporter: sunjincheng
> Assignee: sunjincheng
> Priority: P2
> Labels: stale-assigned
> Fix For: Not applicable
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> In the runner document, it is described that we can use the command:
> `./gradlew :sdks:python:container:docker`
> to Build the SDK harness container, see
> ([https://beam.apache.org/documentation/runners/flink/)].
> However, the docker config has been removed with the latest python3 docker
> related commit [1] the command would failed with the following error message.
> {code:java}
> > Task :sdks:python:container:docker FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':sdks:python:container:docker'.
> > name is a required docker configuration item.{code}
> I think we should also adapt the document with command: `./gradlew
> :sdks:python:container:py2:docker`? Or add the config when run
> `:sdks:python:container:docker` auto run all the python version docker?
>
> What do you think?
>
> [1]
> [https://github.com/apache/beam/commit/47feeafb21023e2a60ae51737cc4000a2033719c#diff-1bc5883bcfcc9e883ab7df09e4dcddb0L63]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
