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

  1. Sign in to your Google Account.

    If you don't already have one, sign up for a new account.

  2. In the Cloud Console, on the project selector page, select or create a Cloud project.

    Go to the project selector page

  3. Make sure that billing is enabled for your Google Cloud project. Learn how to confirm billing is enabled for your project.

Deploying the sample container

To deploy a container:

  1. Go to Cloud Run

  2. Click Create service to display the Create service form:

    image

    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. Select Allow unauthenticated invocations to be able to open the result in your web browser

    5. Click Next to continue to the second page of the service creation form:

      image

      In the form,

      1. Use gcr.io/cloudrun/hello as a container image.

      2. Click Create to deploy the image to Cloud Run and wait for the deployment to finish.

  3. 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-southeast1 (Singapore)
  • australia-southeast1 (Sydney)
  • northamerica-northeast1 (Montreal)

Note that it is not possible to use the domain mapping feature of Cloud Run (fully managed) for services in asia-northeast2, australia-southeast1 or northamerica-northeast1. You can use Cloud Load Balancing with a serverless NEG to map a custom domain to Cloud Run (fully managed) services in these regions.

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 up to handle the received requests, then scales down 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: