No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

```#Seting up the state file 
pulumi login ${PULUMI_BACKEND_URL}

#selecting a stack 
pulumi stack select ${PULUMI_STACK} --non-interactive
pulumi config set --path gcpconfig:test.name ${TEST_SERVICE}
pulumi refresh -y --non-interactive
pulumi preview --non-interactive 
pulumi up -f -y --non-interactive```
These are my entry point commands and i get the error

```go build <http://github.com/pulumi/pulumi-gcp/sdk/v4/go/gcp/compute|github.com/pulumi/pulumi-gcp/sdk/v4/go/gcp/compute>: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed

    error: an unhandled error occurred: program exited with non-zero exit code: 1```


<@U01HRVARTC7> it looks like it's being killed because the docker vm is running out of memory when compiling the go code

image.png

<@UCWG26BH7> - Let me take a look .. thanks for the direction

Screenshot 2021-03-24 at 6.40.51 AM.png

Screenshot 2021-03-24 at 6.42.38 AM.png

Am not sure why is there a build step . Am using go mod which downloads all the necessary binaries

pulumi builds your go project into a binary before it executes

<https://stackoverflow.com/questions/52129612/golang-circleci-2-0-test-failing-with-signal-killed>

yup it worked with 12 GB of ram ---&gt; :eyes: