Skip to content

build: bump Cloud Build machineType to E2_HIGHMEM_32 - #5882

Closed
cuixq wants to merge 2 commits into
google:masterfrom
cuixq:machine
Closed

build: bump Cloud Build machineType to E2_HIGHMEM_32#5882
cuixq wants to merge 2 commits into
google:masterfrom
cuixq:machine

Conversation

@cuixq

@cuixq cuixq commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Another try for #5692

Cloud Build steps building Go images (such as build-importer) have been intermittently failing with the following error:

ERROR: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: frontend grpc server closed unexpectedly

The current machine type E2_HIGHCPU_32 provides 32 vCPUs but only 32 GB of RAM (1 GB per core). During concurrent Go builds and module downloads, sudden memory spikes may trigger Linux OOM kills on ephemeral Docker BuildKit helper containers (gateway.v0), causing the gRPC connection to abruptly terminate.

Bump Cloud Build machineType in deployment/build-and-stage.yaml from E2_HIGHCPU_32 (32 GB RAM) to E2_HIGHMEM_32 (256 GB RAM).

@cuixq
cuixq marked this pull request as ready for review August 21, 2026 00:27
@michaelkedar

Copy link
Copy Markdown
Member

Looking at the Cloud Build pricing page, it doesn't seem like E2_HIGHMEM_32 is an available option without setting up a private pool

@cuixq cuixq closed this Aug 21, 2026
@cuixq
cuixq deleted the machine branch August 21, 2026 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants