Argo-cd: Installation fails due to rate limits

Created on 26 Nov 2020  路  5Comments  路  Source: argoproj/argo-cd

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

  • [X] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • [X] I've included steps to reproduce the bug.
  • [ ] I've pasted the output of argocd version.

Describe the bug

The installation fails due to rate limits on Docker Hub:

~
Failed to pull image "argoproj/argocd@sha256:b835999eb5cf75d01a2678cd971095926d9c2566c9ffe746d04b83a6a0a2849f": rpc error: code = Unknown desc = Error reading manifest sha256:b835999eb5cf75d01a2678cd971095926d9c2566c9ffe746d04b83a6a0a2849f in docker.io/argoproj/argocd: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
~

To Reproduce

Pull images.

Expected behavior

It would be great to provide an alternate location of the container images, which doesn't have such tight rate limits.

Screenshots

See above

Version

Paste the output from `argocd version` here.

Logs

Failed to pull image "argoproj/argocd@sha256:b835999eb5cf75d01a2678cd971095926d9c2566c9ffe746d04b83a6a0a2849f": rpc error: code = Unknown desc = Error reading manifest sha256:b835999eb5cf75d01a2678cd971095926d9c2566c9ffe746d04b83a6a0a2849f in docker.io/argoproj/argocd: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

bug

Most helpful comment

FYI, I just submitted an application to have argoproj exempted from the limit.

image

All 5 comments

Agree, this is bad. We are currently evaluating a target registry for migration of the images.

/cc @jessesuen @alexmt @edlee2121

FYI, I just submitted an application to have argoproj exempted from the limit.

image

@edlee2121 shall we start moving all our images to google container registry and changing default instal manifests to use it?

Another option is github container registry, although it's a bit unproven.

@jessesuen That's not a bad option. Your call. If you decide to move it, please ensure you setup appropriate access controls.

GitHub container repository (https://ghcr.io) works quite well, as does https://quay.io

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rosscdh picture rosscdh  路  3Comments

eroji picture eroji  路  3Comments

ksaito1125 picture ksaito1125  路  3Comments

travis-sobeck picture travis-sobeck  路  3Comments

alexec picture alexec  路  3Comments