Cloud Run: Revision 'svc-00005' is not ready — Image 'gcr.io/proj/app:latest' not found / Permission 'artifactregistry.repositories.downloadArtifacts' denied
Cloud Run cannot pull the container image — it doesn't exist, the tag is wrong, or the service identity lacks access to the registry.
Revision is not ready and cannot serve traffic. Image not foundImage 'gcr.io/' not found Cloud RunCloud Run Revision is not ready and cannot serve traffic. Image ... not foundContainer manifest type must support amd64/linuxfailed to pull image Cloud Run Meaning
Check the exact image path and tag/digest in Artifact Registry, that the image was pushed to the same project/region, and that Cloud Run's service agent (or the runtime service account) can read the repository (roles/artifactregistry.reader). Cross-project images need access granted to the Cloud Run service agent.
Common causes
- Wrong image name, tag or region
- Image never pushed (build failed)
- Cloud Run service agent lacks reader role on the repo
- Image in another project
- Image built for the wrong CPU architecture (arm64 on Mac M1)
⚡ Quick fix
gcloud artifacts docker images list REPOto confirm- Grant
roles/artifactregistry.readerto the Cloud Run service agent - Build for linux/amd64:
docker buildx build --platform linux/amd64
Detailed fix by platform
gcloud
gcloud artifacts docker images list europe-docker.pkg.dev/PROJECT/REPO
How to diagnose
- Image — Exists at that path?
- Access — Reader role?
- Arch — amd64?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Artifact Registry: Permission artifactregistry.repositories.uploadArtifacts denied Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r"
- Cloud Run 403: Your client does not have permission to get URL Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server
- Cloud Run 503: The request failed because the instance had an error Cloud Run: 503 Service Unavailable — The request was aborted because there was no available instance
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Could not load the default credentials Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
- BigQuery: Access Denied: Project: User does not have bigquery.jobs.create permission BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026