Juju core k8s charm container image is hosted on dockerhub hitting rate limits
Bug #2052997 reported by
Rob Gibbon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Running Juju 3.3, I'm hitting dockerhub API rate limits on my JuJu k8s environment. Dockerhub seems a poor choice to host core Juju images.
I expect Juju to just work without me having to have an account or take out a subscription to dockerhub. I'd that's not the case, then the documentation should be updated to clearly explain that users require a dockerhub subscription.
To post a comment you must log in.
dockerhub has been in use since before rate limits were introduced. We ultimately want to use the rock infrastructure to serve the images. But until that's ready, we also publish to ghcr and ecr, and you can select one of those at bootstrap using
--config caas-image- repo="public. ecr.aws/ juju"
or
--config caas-image- repo="ghcr. io/juju"
as a bootstrap option.
We will need to check the doc to make sure it covers this.