Assigned
Status Update
Comments
sj...@google.com <sj...@google.com> #3
Hi, this error only affects Cloud SDK version 186. It was previously reported in Issue 72407295 and a fix for it should be released in Cloud SDK version 187.
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
Description
In order to speed up builds i would like the possibility to pre-provision our custom build steps on cloud builder VMs.
They come pre loaded with quite a big list of images (all the default build-steps, but also debian, ubuntu, centos and others)
What i currently do is base my build-step of of one of these preloaded images which contains as much of the things i need. That way only a few small layers need to be pulled in.
The problem here is that the preloaded images are updated regularly (at an unknown schedule) and the layers hashes then change. Causing the pull of our custom-build step to pull in all the layers, even though identical layers might be already present.
We have a few based off of the gcloud image build step, which weighs in at over 1Gb, last time i checked, and these builds become extremely slow, until i rebuild the custom build step to use the new pre provisioned image as a base.
Cheers,
Dennis