Why Cloud Run matters for containers in GCP - Why It Works

Introduction

Running container apps can be hard because you need to manage servers and scaling. Cloud Run solves this by running containers automatically without you managing servers, so your app just works and scales with demand.

When you want to run a containerized web app without managing servers or infrastructure.

When your app needs to automatically scale up and down based on traffic without manual setup.

When you want to deploy a container quickly from your local machine or CI/CD pipeline.

When you want to pay only for the exact time your container is handling requests.

When you want to focus on writing code and not worry about server maintenance or patching.

Commands

This command deploys a container image to Cloud Run as a managed service in the us-central1 region and allows public access.

Terminal

gcloud run deploy example-service --image=gcr.io/cloudrun/hello --region=us-central1 --platform=managed --allow-unauthenticated

Expected Output

Deploying container to Cloud Run service [example-service] in project [your-project-id] region [us-central1]



✔ Deploying new service... Done.

  ✔ Creating Revision...

  ✔ Routing traffic...

  ✔ Setting IAM Policy...



Service [example-service] revision [example-service-00001-abc] has been deployed and is serving 100 percent of traffic.



Service URL: https://example-service-abcde.a.run.app

→

--image - Specifies the container image to deploy.

→

--platform - Specifies Cloud Run managed platform.

→

--allow-unauthenticated - Allows public access to the service.

Lists all Cloud Run services deployed in the us-central1 region to verify the deployment.

Terminal

gcloud run services list --platform=managed --region=us-central1

Expected Output

SERVICE          REGION        URL

example-service  us-central1   https://example-service-abcde.a.run.app

→

--platform - Specifies Cloud Run managed platform.

→

--region - Specifies the region to list services from.

Sends a request to the deployed Cloud Run service URL to check if the container is running and responding.

Terminal

curl https://example-service-abcde.a.run.app

Expected Output

Hello World!

Key Concept

If you remember nothing else from this pattern, remember: Cloud Run lets you run containers easily without managing servers, and it automatically scales your app with traffic.

Common Mistakes

Not specifying the --platform=managed flag when deploying.

Cloud Run defaults to different platforms; missing this flag can deploy to the wrong environment or fail.

Always include --platform=managed to deploy to the fully managed Cloud Run service.

Forgetting to allow unauthenticated access with --allow-unauthenticated.

Without this flag, the service is private and cannot be accessed publicly, causing connection errors.

Add --allow-unauthenticated if you want your service to be publicly accessible.

Using a container image that is not accessible or does not exist.

Cloud Run cannot deploy if the image URL is wrong or the image is private without proper permissions.

Use a valid, publicly accessible container image or configure permissions correctly.

Summary

Use 'gcloud run deploy' to deploy your container image to Cloud Run with automatic scaling.

Verify your service with 'gcloud run services list' to see deployed services and URLs.

Test your running container by sending a request to the service URL with curl.

Practice

1. What is the main benefit of using Cloud Run for container applications?

easy

A. It charges a fixed monthly fee regardless of usage.

B. It requires you to manage the underlying servers manually.

C. It only works with virtual machines, not containers.

D. It automatically scales your containers based on traffic.

Solution

1. Step 1: Understand Cloud Run's scaling feature

   Cloud Run automatically adjusts the number of container instances based on incoming traffic, so you don't have to manage scaling yourself.

2. Step 2: Compare other options

   Cloud Run does not require manual server management, works specifically with containers (not virtual machines), and charges based on usage, not a fixed fee.

3. Final Answer:

   It automatically scales your containers based on traffic. -> Option D

4. Quick Check:

   Automatic scaling = A [OK]

Hint: Cloud Run scales containers automatically with traffic [OK]

Common Mistakes:

• Thinking Cloud Run requires manual server management
• Confusing Cloud Run with virtual machine services
• Assuming fixed pricing regardless of usage

2. Which of the following is the correct way to deploy a container to Cloud Run using the gcloud CLI?

easy

A. gcloud app deploy --image gcr.io/my-project/my-image

B. gcloud compute instances create --image gcr.io/my-project/my-image

C. gcloud run deploy my-service --image gcr.io/my-project/my-image --platform managed

D. gcloud container clusters create --image gcr.io/my-project/my-image

Solution

1. Step 1: Identify the correct command for Cloud Run deployment

   The command to deploy a container to Cloud Run is gcloud run deploy my-service --image gcr.io/my-project/my-image --platform managed.

2. Step 2: Eliminate incorrect commands

   gcloud compute instances create is for Compute Engine, gcloud container clusters create for Kubernetes clusters, and gcloud app deploy for App Engine, none for Cloud Run.

3. Final Answer:

   gcloud run deploy my-service --image gcr.io/my-project/my-image --platform managed -> Option C

4. Quick Check:

   Cloud Run deploy uses 'gcloud run deploy' [OK]

Hint: Use 'gcloud run deploy' with --image for Cloud Run [OK]

Common Mistakes:

• Using Compute Engine or Kubernetes commands instead
• Confusing App Engine deploy command with Cloud Run
• Omitting the --platform managed flag

3. You want to run a containerized web app that only needs to be active during user requests and should scale down to zero when idle to save costs. Which Cloud Run feature best supports this requirement?

easy

A. Cloud Run's fixed instance count setting.

B. Cloud Run's automatic scaling to zero instances when idle.

C. Cloud Run's manual server provisioning.

D. Cloud Run's requirement to keep at least one instance always running.

Solution

1. Step 1: Identify cost-saving scaling feature

   Cloud Run automatically scales down to zero instances when there is no traffic, which saves costs by not running containers unnecessarily.

2. Step 2: Confirm this matches the app requirement

   The app needs to be active only during user requests and idle otherwise, so automatic scaling to zero fits perfectly.

3. Final Answer:

   Cloud Run's automatic scaling to zero instances when idle. -> Option B

4. Quick Check:

   Scale to zero for cost saving = A [OK]

Hint: Use Cloud Run's scale-to-zero for cost-efficient apps [OK]

Common Mistakes:

• Thinking fixed instance count saves costs
• Assuming manual provisioning is needed
• Believing one instance must always run

4. Consider this scenario: You deploy a container to Cloud Run. The container receives no traffic for a while, then suddenly gets a burst of requests. What happens to the container instances?

medium

A. Cloud Run scales down to zero instances when idle, then scales up quickly on new requests.

B. Cloud Run crashes the container if no traffic is received for 5 minutes.

C. Cloud Run keeps all container instances running regardless of traffic.

D. Cloud Run requires manual scaling to handle traffic bursts.

Solution

1. Step 1: Understand Cloud Run's scaling behavior

   Cloud Run automatically scales down to zero instances when there is no traffic to save resources and costs.

2. Step 2: Understand scaling up on traffic burst

   When new requests arrive, Cloud Run quickly starts new container instances to handle the traffic burst automatically.

3. Final Answer:

   Cloud Run scales down to zero instances when idle, then scales up quickly on new requests. -> Option A

4. Quick Check:

   Scale to zero and up on demand = C [OK]

Hint: Cloud Run scales to zero when idle, then up on traffic [OK]

Common Mistakes:

• Assuming containers always run even with no traffic
• Thinking Cloud Run crashes containers on idle
• Believing manual scaling is needed for traffic bursts

5. You deployed a container to Cloud Run but it fails to start. The error says the container does not listen on the expected port. What is the likely cause?

medium

A. Cloud Run requires containers to listen on the port defined by the PORT environment variable.

B. Cloud Run only supports containers that listen on port 80 hardcoded.

C. Cloud Run does not allow containers to listen on any port.

D. Cloud Run automatically assigns a random port and no configuration is needed.

Solution

1. Step 1: Identify Cloud Run port requirement

   Cloud Run expects containers to listen on the port specified by the PORT environment variable it sets.

2. Step 2: Understand common error cause

   If the container listens on a different port, Cloud Run cannot route traffic correctly, causing startup failure.

3. Final Answer:

   Cloud Run requires containers to listen on the port defined by the PORT environment variable. -> Option A

4. Quick Check:

   Listen on PORT env variable = B [OK]

Hint: Containers must listen on PORT env variable in Cloud Run [OK]

Common Mistakes:

• Assuming port 80 is always used
• Thinking Cloud Run forbids listening on ports
• Believing no port configuration is needed