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

use dockerhub busybox image #181

Closed
js-9 opened this issue Jul 22, 2022 · 3 comments
Closed

use dockerhub busybox image #181

js-9 opened this issue Jul 22, 2022 · 3 comments

Comments

@js-9
Copy link
Contributor

js-9 commented Jul 22, 2022

My install to an arm cluster went surprisingly well. The only thing that failed was the busybox docker image pull since gcr docker registry doesn't support multiarch images and it doesn't contain an arm image for busybox. Setting the helm variable to use just the "busybox" image fixed this issue, so I would propose to just use that.

@senthilrch
Copy link
Owner

@js-9 : Thanks for raising this issue. I understand the busybox image in gcr doesn't supports arm architecture. By default, kube-fledged doesn't uses the busybox image from dockerhub because the pulls are subject to ratelimiting.

I've copied the busybox:1.35.0 image from dockerhub to senthilrch/busybox:1.35.0 in dockerhub. The "senthilrch" namespace in dockerhub is exempted from ratelimiting. I've modified kube-fledged to use senthilrch/busybox:1.35.0 by default; this will fix the issue you faced with installing kube-fledged in arm cluster.

@senthilrch
Copy link
Owner

This will be available in v0.10.0

@js-9
Copy link
Contributor Author

js-9 commented Oct 18, 2022

Thank you Senthil!

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 a pull request may close this issue.

2 participants