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

toomanyrequests error from docker.io when running GitHub action test.yaml #1717

Open
brooke-hamilton opened this issue Aug 16, 2024 · 0 comments
Labels
bug Something is broken or not working as expected triaged This item has been triaged by project maintainers and is in the backlog

Comments

@brooke-hamilton
Copy link
Contributor

brooke-hamilton commented Aug 16, 2024

Bug information

.github/workflows/test.yaml will sometimes throw a "toomanyrequests" error when pulling container images from docker.io.

Steps to reproduce (required)

Reproducing this error depends on hitting a rate limit with docker.io, which happens when more than 100 pulls are done within six hours.

To reproduce the issue, run the GitHub workflow in .github/workflows/test.yaml, titled "Test Samples (k3d and EKS)".

Observed behavior (required)

In the yaml workflow step named Create k3d cluster, the error below will sometimes appear:

Run k3d cluster create --agents 2 -p "80:80@loadbalancer" --k3s-arg "--disable=traefik@server:*" --k3s-arg "--disable=servicelb@server:*" --registry-create sampleregistry:51351
INFO[0000] portmapping '80:80' targets the loadbalancer: defaulting to [servers:*:proxy agents:*:proxy] 
INFO[0000] Prep: Network                                
INFO[0000] Created network 'k3d-k3s-default'            
INFO[0000] Created image volume k3d-k3s-default-images  
INFO[0000] Creating node 'sampleregistry'               
ERRO[0000] Failed Cluster Preparation: Failed to create registry: failed to create registry node 'sampleregistry': runtime failed to create node 'sampleregistry': failed to create container for node 'sampleregistry': docker failed to pull image 'docker.io/library/registry:2': docker failed to pull the image 'docker.io/library/registry:2': 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 
ERRO[0000] Failed to create cluster >>> Rolling Back    
INFO[0000] Deleting cluster 'k3s-default'               
ERRO[0000] failed to get cluster: No nodes found for given cluster 
FATA[0000] Cluster creation FAILED, also FAILED to rollback changes! 
Error: Process completed with exit code 1.

This is an example of a failed test run: https://github.com/radius-project/samples/actions/runs/10424759874/job/28876734613

Desired behavior (required)

The workflow should be runnable without hitting a rate limit.

Workaround (optional)

A possible workaround is to configure all the container pulls in the workflow to pull from a different registry.

System information

rad Version (required)

VERSION=0.37.0-rc1

Operating system (required)

GitHub action runner

AB#12993

@brooke-hamilton brooke-hamilton added the bug Something is broken or not working as expected label Aug 16, 2024
@lakshmimsft lakshmimsft added the triaged This item has been triaged by project maintainers and is in the backlog label Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken or not working as expected triaged This item has been triaged by project maintainers and is in the backlog
Projects
None yet
Development

No branches or pull requests

2 participants