.gitlab-ci.yml: use the Docker image from gitlab registry
From [1]: "In November 2020, Docker introduced rate limits on pull requests from Docker Hub [2]. If your GitLab CI/CD configuration uses an image from Docker Hub, each time a job runs, it may count as a pull request." Since then, some jobs in our gitlab-ci fail when this rate limits is reached [3]. To avoid this rate limit, move our Docker image from dockerhub to the registry provided by gitlab. Keeping the image from dockerhub would be possible by using dependency proxy [4] but the gitlab registry is good enough. Tested on gitlab: https://gitlab.com/kubu93/buildroot/-/jobs/1694863584 [1] https://docs.gitlab.com/ee/user/packages/container_registry/index.html [2] https://docs.docker.com/docker-hub/download-rate-limit/ [3] https://gitlab.com/buildroot.org/buildroot/-/jobs/1687590417 [4] https://docs.gitlab.com/ee/user/packages/dependency_proxy Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This commit is contained in:
parent
86b77153b2
commit
b3b4e270d1
@ -1,7 +1,7 @@
|
||||
# Configuration for Gitlab-CI.
|
||||
# Builds appear on https://gitlab.com/buildroot.org/buildroot/pipelines
|
||||
|
||||
image: buildroot/base:20210922.2200
|
||||
image: $CI_REGISTRY/buildroot.org/buildroot/base:20210922.2200
|
||||
|
||||
stages:
|
||||
- generate-gitlab-ci
|
||||
|
Loading…
Reference in New Issue
Block a user