Kaniko fails to 'warm' or build from existing cache due to docker hub's rate-limiting #3063
Labels
area/caching
For all bugs related to cache issues
differs-from-docker
feat/warmer
gitlab
kind/bug
Something isn't working
priority/p1
Basic need feature compatibility with docker build. we should be working on this next.
Actual behavior
While running the the warmer in our GitLab CI/CD we quickly hit the rate-limiting with docker hub even though the cache is warmed already.
GitLab CI:
First run:
Second run (~10mins later):
Or the build:
Note: I also tried it with a different approach of running the warmer only once, which in the end tries to pull less images but else does not change anything:
Expected behavior
Pipeline succeeds because manifests of base images are already present in the mounted cache. Note that there is one single runner VM, so the cache is present.
Not sure, but maybe this could be achieved by using the
HEAD
request instead ofGET
(https://docs.docker.com/docker-hub/download-rate-limit/)?To Reproduce
Steps to reproduce the behavior:
Additional Information
They are templated, which is why we loop them and add them all to the cache, but there is always only one single
FROM
entry in the files, in most cases even the same:FROM registry.hub.docker.com/library/rockylinux:9
andFROM registry.hub.docker.com/library/rockylinux:8
Only local files
From the Pipeline:
Using docker image sha256:b2f0e64d2a66329ae9b6eebd73d688625d6943328205d8471755cea6edbc9536 for gcr.io/kaniko-project/executor:debug with digest gcr.io/kaniko-project/executor@sha256:0818d281f155b9bb1b1f0704e55939b9c440b0155cbbf65b567ca19e19e20223
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: