non cloud functional tests sometimes fail with a 429 too many requests

[nithyatsu]

sample run is https://github.com/radius-project/radius/actions/runs/11331604413/job/31512006276

We sometimes hit a limit while pulling golang1.22-alpine with below error:

[https://registry-ERROR: failed to solve: golang:1.22-alpine: failed to resolve source metadata for docker.io/library/golang:1.22-alpine: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/golang/manifests/sha256:f56a8a4a1aea41bc4694728b69c219af1523aea15690cbbed82dc9bac81e6603: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
make: *** [build/docker.mk:117: docker-build-magpiego] Error 1
Error: Process completed with exit code 2.

we could improve the limit with authenticated pulls or ignore the error and wait for the next functional run.

AB#13569

[sylvainsf]

This should be evaluated/fixed by on-call

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview