My application deployment pipeline utilizes GCP triggers and Cloud Build. However, the Cloud Build process is currently experiencing following error.

Step #0: 
Step #0: Total reclaimed space: 69.96GB
Finished Step #0
Starting Step #1
Step #1: Pulling image: gcr.io/google/cloudsdktool/cloud-sdk
ERROR: failed to pull because we ran out of retries.
ERROR
ERROR: build step 1 "gcr.io/google/cloudsdktool/cloud-sdk" failed: error pulling build step 1 "gcr.io/google/cloudsdktool/cloud-sdk": retry budget exhausted (10 attempts): starting container: Error response from daemon: No such image: gcr.io/cloud-builders/gcb-internal:latest

Following is the section of Build script that is failing:

steps:
  - name: gcr.io/cloud-builders/docker
    args:
      - '-c'
      - |
        docker system prune -af --volumes
    entrypoint: bash
  - name: 'gcr.io/google/cloudsdktool/cloud-sdk'
    args:
      - '-c'
      - >

The pipeline has been operating smoothly until recently, when it began experiencing failures with the aforementioned error message.

Any help is highly appreciated in this regard.

My application deployment pipeline utilizes GCP triggers and Cloud Build. However, the Cloud Build process is currently experiencing following error.

Step #0: 
Step #0: Total reclaimed space: 69.96GB
Finished Step #0
Starting Step #1
Step #1: Pulling image: gcr.io/google/cloudsdktool/cloud-sdk
ERROR: failed to pull because we ran out of retries.
ERROR
ERROR: build step 1 "gcr.io/google/cloudsdktool/cloud-sdk" failed: error pulling build step 1 "gcr.io/google/cloudsdktool/cloud-sdk": retry budget exhausted (10 attempts): starting container: Error response from daemon: No such image: gcr.io/cloud-builders/gcb-internal:latest

Following is the section of Build script that is failing:

steps:
  - name: gcr.io/cloud-builders/docker
    args:
      - '-c'
      - |
        docker system prune -af --volumes
    entrypoint: bash
  - name: 'gcr.io/google/cloudsdktool/cloud-sdk'
    args:
      - '-c'
      - >

The pipeline has been operating smoothly until recently, when it began experiencing failures with the aforementioned error message.

Any help is highly appreciated in this regard.

• google-cloud-platform
• triggers
• virtual-machine
• google-cloud-sdk

Share Improve this question Follow asked Mar 25 at 3:27 Farooq ZamanFarooq Zaman 50711 gold badge66 silver badges2222 bronze badges 1

• Please edit the question by sharing detailed steps along with the documentation that anyone can use to replicate the behavior? Also make sure the image name in your cloudbuild.yaml file is correct. Check whether you are able to access the image gcr.io/google/cloudsdktool/cloud-sdk directly from a machine. – Sandeep Vokkareni Commented Mar 25 at 9:03

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

It's because of the pruning.

It wasn't an issue in the past, now it is.

Had this issue for a week, maybe it appeared even earlier. Something on Google Cloud's side suddenly broke and you can no longer pull some public images like "bash" or "gcr.io/cloud-builders/gcloud".

For now, you'll have to remove the pruning step.