Bird
0
0

You deployed a container to Cloud Run but it fails immediately with an error. What is a common cause?

medium📝 Debug Q6 of 15
GCP - Cloud Run
You deployed a container to Cloud Run but it fails immediately with an error. What is a common cause?
ACloud Run does not support environment variables
BContainer does not listen on the expected port
CCloud Run requires containers to be written in Go
DContainer image is too large
Step-by-Step Solution
Solution:

  1. Step 1: Identify common deployment errors

    Containers must listen on the port Cloud Run expects, or they fail to start properly.

  2. Step 2: Exclude incorrect causes

    Container size, language, and environment variables are not typical immediate failure causes.

  3. Final Answer:

    Container does not listen on the expected port -> Option B

  4. Quick Check:

    Port listening mismatch causes startup failure [OK]
Quick Trick: Check container listens on Cloud Run's PORT env variable [OK]
Common Mistakes:
  • Blaming container size for startup failure
  • Thinking Cloud Run limits programming languages
  • Assuming environment variables are unsupported

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes
Cloud Firestore and Bigtable - Firestore document model - Quiz 15hard Cloud Firestore and Bigtable - Firestore collections and documents - Quiz 12easy Cloud IAM Advanced - Data access logs - Quiz 15hard Cloud Load Balancing - Load balancer types comparison - Quiz 6medium Cloud Load Balancing - HTTP(S) Load Balancer (Layer 7) - Quiz 14medium Cloud Load Balancing - Load balancer types comparison - Quiz 1easy Cloud Monitoring and Logging - Why observability matters - Quiz 9hard Cloud Monitoring and Logging - Why observability matters - Quiz 6medium Cloud Pub/Sub - Message retention and acknowledgment - Quiz 6medium Cloud SQL and Databases - Cloud Spanner for global distribution - Quiz 11easy