Cloud build cache images [122940367]

Assigned

Feature Request

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Jan 16, 2019 06:54PM

A lot of my build time is spent on fetching docker images and it would be great if the images could be cached between invocations of the build and not between steps.
steps:
- name: 'big image' < I want to pull this one faster.

Also can the logs of pulling/pushing layers be hidden, it bloats down the log a lot.

Step #1: v1: Pulling from image < Keep

Step #1: c64513b74145: Pulling fs layer < Remove
Step #1: 01b8b12bad90: Pulling fs layer
Step #1: c5d85cf7a05f: Pulling fs layer
Step #1: b6b268720157: Pulling fs layer
Step #1: e12192999ff1: Pulling fs layer
Step #1: 97fbe2ceb2ba: Pulling fs layer
Step #1: 7e7a116f4014: Pulling fs layer
Step #1: 28d9e4e44578: Pulling fs layer
Step #1: 007b73881093: Pulling fs layer
Step #1: 63499c1f5dd7: Pulling fs layer
Step #1: 61bb193c9330: Pulling fs layer
Step #1: ab6a1d648950: Pulling fs layer
Step #1: 6a83728dffa4: Pulling fs layer
Step #1: 10a1036dd155: Pulling fs layer
Step #1: f15f9b067340: Pulling fs layer
Step #1: b6b268720157: Waiting
Step #1: e12192999ff1: Waiting
Step #1: 7e7a116f4014: Waiting
Step #1: 28d9e4e44578: Waiting
Step #1: 007b73881093: Waiting
Step #1: 63499c1f5dd7: Waiting
Step #1: 61bb193c9330: Waiting
Step #1: ab6a1d648950: Waiting
Step #1: 6a83728dffa4: Waiting
Step #1: 10a1036dd155: Waiting
Step #1: f15f9b067340: Waiting
Step #1: 97fbe2ceb2ba: Waiting
Step #1: 01b8b12bad90: Verifying Checksum
Step #1: 01b8b12bad90: Download complete
Step #1: c5d85cf7a05f: Verifying Checksum
Step #1: c5d85cf7a05f: Download complete
Step #1: e12192999ff1: Verifying Checksum
Step #1: e12192999ff1: Download complete
Step #1: b6b268720157: Verifying Checksum
Step #1: b6b268720157: Download complete
Step #1: 7e7a116f4014: Verifying Checksum
Step #1: 7e7a116f4014: Download complete
Step #1: c64513b74145: Verifying Checksum
Step #1: c64513b74145: Download complete
Step #1: 007b73881093: Download complete
Step #1: 28d9e4e44578: Verifying Checksum
Step #1: 28d9e4e44578: Download complete
Step #1: 63499c1f5dd7: Verifying Checksum
Step #1: 63499c1f5dd7: Download complete
Step #1: 61bb193c9330: Verifying Checksum
Step #1: 61bb193c9330: Download complete
Step #1: c64513b74145: Pull complete
Step #1: 01b8b12bad90: Pull complete
Step #1: c5d85cf7a05f: Pull complete
Step #1: 6a83728dffa4: Verifying Checksum
Step #1: 6a83728dffa4: Download complete
Step #1: 97fbe2ceb2ba: Verifying Checksum
Step #1: 97fbe2ceb2ba: Download complete
Step #1: b6b268720157: Pull complete
Step #1: e12192999ff1: Pull complete
Step #1: 10a1036dd155: Verifying Checksum
Step #1: 10a1036dd155: Download complete
Step #1: f15f9b067340: Verifying Checksum
Step #1: f15f9b067340: Download complete
Step #1: ab6a1d648950: Verifying Checksum
Step #1: ab6a1d648950: Download complete
Step #1: 97fbe2ceb2ba: Pull complete
Step #1: 7e7a116f4014: Pull complete
Step #1: 28d9e4e44578: Pull complete
Step #1: 007b73881093: Pull complete
Step #1: 63499c1f5dd7: Pull complete
Step #1: 61bb193c9330: Pull complete
Step #1: ab6a1d648950: Pull complete
Step #1: 6a83728dffa4: Pull complete
Step #1: 10a1036dd155: Pull complete
Step #1: f15f9b067340: Pull complete < Remove
Step #1: Digest: sha256:hash < Keep
Step #1: Status: Downloaded newer image for image:v1 < Keep

Comments

da...@google.com <da...@google.com> #2Jan 23, 2019 02:10PM

Assigned to da...@google.com.

Duplicate of

https://issuetracker.google.com/issues/72407295

jo...@gmail.com <jo...@gmail.com> #3Jan 23, 2019 02:19PM

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

da...@google.com <da...@google.com> #4Jan 24, 2019 03:46PM

Hello,

Instead of a flag, do you think an option that you could enable/disable to hide these build steps in the Cloud Console’s UI specifically next to the "Logs" section would suffice for your use case?

jo...@gmail.com <jo...@gmail.com> #5Jan 24, 2019 04:43PM

Yes it will be great.

da...@google.com <da...@google.com> #6Jan 25, 2019 04:09PM

Reassigned to gc...@google.com.

Hello,

I have created a feature request which you can follow [1]. There is currently no ETA or guarantee of implementation. All further updates should occur in [1].

[1]

https://issuetracker.google.com/123400790

Issue 122940367