UPDATE: Indeed, it turns out that the issue is I built the Docker container on an M1 and CloudRun only works if you built your container with "--platform linux/

UPDATE: Indeed, it turns out that the issue is I built the Docker container on an M1 and CloudRun only works if you built your container with "--platform linux/amd64" ====== > no VPC connector is needed. That's not true. It's enough that Google has released 2 forms of docs on this matter. Additionally, the webform to provision CloudRun also includes a section on VPC Connectors. You need to provision a VPC connector in order for CloudRun, Functions or App Engine to "see" CloudSQL with private IP. https://codelabs.developers.google.com/connecting-to-private-cloudsql-from-cloud-run#0 https://codelabs.developers.google.com/connecting-to-private... The VPC connector is a product which is backed by VMs. Its provisioning / validation rules require at least 2 VMs. You can see the web form yourself: https://console.cloud.google.com/networking/connectors/add?project=$YOUR_PROJECT_ID https://console.cloud.google.com/networking/connectors/add?p... > but that is abstracted and won't be in your list Yes, that's abstracted but you are billed for the vCores. You can see the price sheets and minimum monthly costs here: https://cloud.google.com/sql/pricing https://cloud.google.com/sql/pricing In the case of CloudSQL, sure, it's abstracted, but CloudRun is revealing its leaky abstraction. Here are implementation details you have to know about: https://cloud.google.com/run/docs/container-contract https://cloud.google.com/run/docs/container-contract. For example, it seems my issue could be related to building the container on an M1 mac. https://stackoverflow.com/questions/66127933/cloud-run-failed-to-start-and-then-listen-on-the-port-defined-by-the-port-envi https://stackoverflow.com/questions/66127933/cloud-run-faile...