-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix docker rate limit #184
Fix docker rate limit #184
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@UnmeshDeodhar, although the patch is good, the commit message is not.
I'd suggest changing the commit message to something like:
tests: Use a specific version of the registry container
Switch to a fixed version of the registry containers, so a new version is not pulled
in every time a test runs, avoiding then hitting the docker hub rate limit.
670d915
to
a2d8776
Compare
/test |
1 similar comment
/test |
@UnmeshDeodhar, almost there, but it's still a very long line. Mind to break it as shown below?
|
Switch to a fixed version of the registry containers, so a new version is not pulled in every time a test runs, avoiding then hitting the docker hub rate limit. Fixes: confidential-containers#182 Signed-off-by: Unmesh Deodhar <udeodhar@amd.com>
a2d8776
to
42e8c28
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @UnmeshDeodhar !
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @UnmeshDeodhar!
Changing registry to a fixed version so that we will not hit the docker hub rate limit.
Fixes: #182