Setting Up Your Environment

Sign in to your Google Account.
If you don't already have one, sign up for a new account.
In the Google Cloud Console, on the project selector page, select or create a Google Cloud project.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to the project selector page
Make sure that billing is enabled for your Cloud project. Learn how to confirm that billing is enabled for your project.
Enable the Cloud Run API
Install and initialize the Cloud SDK.
Update components:
```
gcloud components update
```
Optionally, set your platform and default Cloud Run region with the gcloud properties to avoid prompts from the command line:
```
gcloud config set run/platform managed
gcloud config set run/region REGION
```
replacing REGION with the default region you want to use.
Optionally, install Docker to build Docker containers locally. If you do so, you must invoke the following gcloud commands to add the gcloud Docker credential helper:
```
gcloud auth configure-docker
gcloud components install docker-credential-gcr
```
For more information about Docker credential helpers, see the documentation for the docker-credential-gcr project.

Cloud Run regions

Cloud Run is regional, which means the infrastructure that runs your Cloud Run services is located in a specific region and is managed by Google to be redundantly available across all the zones within that region.

Meeting your latency, availability, or durability requirements are primary factors for selecting the region where your Cloud Run services are run. You can generally select the region nearest to your users but you should consider the location of the other Google Cloud products that are used by your Cloud Run service. Using Google Cloud products together across multiple locations can affect your service's latency as well as cost.

Cloud Run is available in the following regions:

Subject to Tier 1 pricing

asia-east1 (Taiwan)
asia-northeast1 (Tokyo)
asia-northeast2 (Osaka)
europe-north1 (Finland)
europe-west1 (Belgium)
europe-west4 (Netherlands)
us-central1 (Iowa)
us-east1 (South Carolina)
us-east4 (Northern Virginia)
us-west1 (Oregon)

Subject to Tier 2 pricing

asia-east2 (Hong Kong)
asia-northeast3 (Seoul, South Korea)
asia-southeast1 (Singapore)
asia-southeast2 (Jakarta)
asia-south1 (Mumbai, India)
australia-southeast1 (Sydney)
europe-west2 (London, UK)
europe-west3 (Frankfurt, Germany)
europe-west6 (Zurich, Switzerland)
northamerica-northeast1 (Montreal)
southamerica-east1 (Sao Paulo, Brazil)

If you already created a Cloud Run service, you can view the region in the Cloud Run dashboard in the Cloud Console.

What's next

To learn how to build a container from code source, push to Container Registry, and deploy, see: