[
https://issues.apache.org/jira/browse/BEAM-12447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412090#comment-17412090
]
Beam JIRA Bot commented on BEAM-12447:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> SdkContainerImageBuilder should take machineType configs
> --------------------------------------------------------
>
> Key: BEAM-12447
> URL: https://issues.apache.org/jira/browse/BEAM-12447
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow, sdk-py-core
> Reporter: Yichi Zhang
> Priority: P2
> Labels: stale-P2
>
> When prebuilding the python SDK container harness image with
> SdkContainerImageBuilder on google cloud build, it can run out of memory and
> fail the build with docker exit code 137. The default machineType is only
> n1-standard-1 and it is unlikely sufficient to build large images.
>
> The SdkContainerImageBuilder should take additional machineType configs to
> circumvent the docker OOM issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
