Quickstart: Deploy a Prebuilt Sample Container

Beta

This product or feature is in a pre-release state and might change or have limited support. For more information, see Product launch stages.

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. Select or create a Google Cloud Platform project.

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

   Go to the Manage resources page

3. Make sure that billing is enabled for your Google Cloud Platform project.

   Learn how to enable billing

Deploying the sample container

To deploy a container:

1. Go to Cloud Run

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

   

   In the form,

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

   2. Select the region where you want your service located.

   3. Check Allow unauthenticated invocations to be able to open the result in your web browser

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

4. 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 GCP products that are used by your Cloud Run service. Using GCP products together across multiple locations can affect your service's latency as well as cost.

Cloud Run is available in the following regions:

• us-central1 (Iowa)

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

OK

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:

• Quickstart: Build and Deploy
• Building Containers