13

I'm following the instructions at https://cloud.google.com/container-builder/docs/speeding-up-builds#using_a_cached_docker_image and I'm trying to setup docker builds that use the image cached from the previous build.

Here's what my cloudbuild.yml looks like:

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['pull', 'gcr.io/$PROJECT_ID/$REPO_NAME:infra_docker']
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '--cache-from', 'gcr.io/$PROJECT_ID/$REPO_NAME:infra_docker', '-t', 'gcr.io/$PROJECT_ID/$REPO_NAME:infra_docker', '.']
timeout: 120m
images: ['gcr.io/$PROJECT_ID/$REPO_NAME:infra_docker']
options:
  machineType: 'N1_HIGHCPU_8'

Here's what my Dockerfile starts with:

FROM ubuntu:14.04
SHELL ["/bin/bash", "-c"]
# lots of RUN commands after this

No matter what I try, the docker image pulled from the cache (as a result of the first step), is not used to speed up the actual docker build (second step). It always runs the entire 38 steps in my Dockerfile!

What am I doing wrong?

Saurabh Nanda
  • 6,373
  • 5
  • 31
  • 60
  • 1
    Everything looks right. It might be a silly suggestion, but do you see "Using cache" for each RUN command? or are you sure they are all being executed? – Phil Nov 13 '18 at 18:12
  • 1
    I have the same problem! 8 months (at the time of writing this) and no answer? I've tried 17.09, and 18.06 – Asfand Qazi Nov 14 '18 at 12:31
  • I've been scratching my head over Docker caching issues with `--cache-from`, I've shared what i've learned here, maybe it can help you to identify the issue: https://stackoverflow.com/a/56024061/149872 I dunno the specifics, but it sounds like the layers from the pulled image aren't the same anymore as the one you're trying to build (this could be for example if the parent image was updated). – Elias Dorneles May 07 '19 at 14:32
  • Beside RUN are you doing a COPY or ADD? Full Dockerfile may help. – Pierre B. May 21 '19 at 08:18
  • Same problem here currently – FaultyJuggler Jun 07 '21 at 21:23

1 Answers1

3

Is the dockerfile multi-stage? I ran into this problem where only the final image is available for caching. Depending on the steps you run, this can appear as if no step is using the cache. If this is the case you need to push the intermediate image(s) to the container registry as well and pull them when building.

Matt
  • 688
  • 5
  • 15
  • 1
    It looks like that this could be the problem, as I run into this problem and use multi-stage builds. It would be great to have pointers on how I can push the intermediate images. I don't know how I can push them – what are their IDs or names? – Luca Steeb Jul 23 '21 at 15:57