Skip to content
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

ci: login to Docker Hub to avoid rate limiting #13830

Closed
wants to merge 1 commit into from

Conversation

MasonM
Copy link
Contributor

@MasonM MasonM commented Oct 29, 2024

Partial fix for #10807

Motivation

E2E test builds are occasionally failing while pulling images from Docker Hub due to rate limiting. Example:

Oct 28 23:30:52 fv-az802-461 k3s[2185]: E1028 23:30:52.151698 2185 kuberuntime_image.go:53] "Failed to pull image" err="Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" image="minio/minio:RELEASE.2022-11-17T23-20-09Z"

As explained in the error, logging in increases the limit.

Modifications

We're already doing this in the "Release" workflow, so this copies that over:

- name: Docker Login
uses: docker/login-action@343f7c4344506bcbf9b4de18042ae17996df046d # v3.0.0
with:
username: ${{ secrets.DOCKERIO_USERNAME }}
password: ${{ secrets.DOCKERIO_PASSWORD }}

Verification

Wait for actions to run

Partial fix for argoproj#10807.

Builds are occasionally failing while pulling images from Docker Hub due
to rate limiting, e.g. https://github.com/argoproj/argo-workflows/actions/runs/11564257560/job/32189242898:
>  Oct 28 23:30:52 fv-az802-461 k3s[2185]: E1028 23:30:52.151698    2185 kuberuntime_image.go:53] "Failed to pull image" err="Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" image="minio/minio:RELEASE.2022-11-17T23-20-09Z"

As explained in the error, logging in increases the limit. We're already
doing this in the "Release" workflow, so this copies that over.

Signed-off-by: Mason Malone <[email protected]>
@MasonM
Copy link
Contributor Author

MasonM commented Oct 29, 2024

Seems it's not working, probably because of "With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository" - https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#using-secrets-in-a-workflow

Not sure if there's anything we can do about this

@MasonM MasonM mentioned this pull request Nov 1, 2024
3 tasks
@MasonM
Copy link
Contributor Author

MasonM commented Nov 1, 2024

#10807 (comment)

@MasonM MasonM closed this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant