Cloud Run local emulator : how to configure memory and CPU?

Question

I'm developing a Cloud Run service using gcloud beta code dev (the local emulator).

• Can I use CLI flags to set memory and CPU?

The docs say there should be a .vscode/launch.json file, but I can't tell

• does this file impact a service launched via gcloud beta code dev, or only from the vscode extension?

• the VSCode extension allows only up to 2048 MiB per instances; can I manually configure more in launch.json? If not, can I configure more via gcloud beta code dev otherwise?

• Can I specify CPUs as well, or are these tied to RAM?

Thanks!

Answer 1

gcloud beta code dev command takes Cloud Run service, builds it and runs it on the local machine. To customize how your service is run, you can specify the following fields in your .vscode/launch.json file including your service name, port, and resource limits. You could also try to configure your service.yaml with gcloud beta code dev. As per gcloud beta code dev doc:

[SERVICE_CONFIG]

service.yaml filename override. Defaults to the first file matching *service.dev.yaml then *service.yaml, if any exist. This path is relative to the --source dir.