Change busybox image registry to avoid rate limit errors #845
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Our tests use a busybox image from dockerhub, however the CI jobs often fail due to rate limit errors. We'll use an image from GHCR instead, where the CI jobs are authenticated.
The tests use images from rocks.canonical.com. We'll configure our proxy to cache images from this registry to reduce the number of image pulls.
petrutlucian94
force-pushed
the
avoid_docker_rate_limit
branch
from
dcc5de7 to
889c9d0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our tests use busybox and nginx images from dockerhub, however the CI jobs often fail due to rate limit errors.
We'll use images from GHCR instead, where the CI jobs are authenticated.
While at it, we'll configure our registry mirror to cache images from rocks.canonical.com.