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

Deployment fails due to dockerhub pull rate limit #88

Closed
mulbc opened this issue Jan 27, 2022 · 2 comments
Closed

Deployment fails due to dockerhub pull rate limit #88

mulbc opened this issue Jan 27, 2022 · 2 comments

Comments

@mulbc
Copy link
Member

mulbc commented Jan 27, 2022

The LVMCluster creation is stuck in a loop, because the topolvm-controller waits for its initContainer, which wants to pull "alpine/openssl".
It fails to pull this container from Dockerhub (the only location where this is available) due to DockerHubs pull rate limite:

Failed to pull image "alpine/openssl": rpc error: code = Unknown desc = initializing source docker://alpine/openssl:latest: reading manifest latest in docker.io/alpine/openssl: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Can we use a different image? As a quick workaround, I rehosted the image at quay.io/mulbc/alpine-openssl

@leelavg
Copy link
Contributor

leelavg commented Jan 28, 2022

@mulbc

  • thanks for raising the issue
  • this is a know issue and more than often kubelet is able to pull the image eventually
  • however, not depending on that, already made changes fix: use operator image for init containers #94 to use same operator image for all supporting containers

@nbalacha
Copy link
Contributor

Closing this issue as the fix has been merged.

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

No branches or pull requests

3 participants