Quickstart: Deploy a Prebuilt Sample Container

This page shows you how to deploy a sample container that has already been uploaded to the Container Registry repository to Cloud Run.

Before you begin

Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
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 project selector
Make sure that billing is enabled for your Cloud project. Learn how to confirm that billing is enabled for your project.

Deploying the sample container

To deploy a container:

Go to Cloud Run
Click Create service to display the Create service form:

In the form,
1. Select Cloud Run (fully managed) as your development platform.
2. Select the region where you want your service located.
3. Specify the name you want to give to your service.
4. Click Next to continue to the Configure the service's first revision page:
  
  In the form,
  1. Select Deploy one revision from an existing container image.
  2. Use us-docker.pkg.dev/cloudrun/container/hello as the container image.
  3. Click Next to continue to the Configure how this service is triggered page:
  4. Select Allow unauthenticated invocations to be able to open the result in your web browser
  5. Click Create to deploy the image to Cloud Run and wait for the deployment to finish.
Click the displayed URL link to run the deployed container.

Cloud Run locations

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-central2 (Warsaw, Poland)
europe-west2 (London, UK)
europe-west3 (Frankfurt, Germany)
europe-west6 (Zurich, Switzerland)
northamerica-northeast1 (Montreal)
southamerica-east1 (Sao Paulo, Brazil)
us-west2 (Los Angeles)
us-west3 (Las Vegas)
us-west4 (Salt Lake City)

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

Congratulations! You have just deployed to Cloud Run a container that responds to incoming web requests. Cloud Run automatically scales your container out to handle the received requests, then scales in when demand decreases. You only pay for the CPU, Memory and Networking consumed during request handling.

What's next

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