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
Clarify usage of registries.conf with different mirrors #1523
Comments
Thanks for reaching out, @telmich! You've found the right place for this kind of question. If you have a dedicated mirror for Docker Hub and a dedicated mirror Quay, an exemplary config may look as follows: [[registry]]
location = "docker.io"
[[registry.mirror]]
location = "docker.mirror.com"
[[registry]]
location = "quay.io"
[[registry.mirror]]
location = "quay.mirror.com" Notice that the mirrors are not global for all registries but are associated with the previous registry. This way, when pulling from Does that answer your question? |
THAT certainly answers the question! OMG, had we known this earlier... So in this regard I suggest to update the documentation to include the notion of "order matters" and maybe even including your example. Thanks a lot for the quick clarification, much appreciated! |
Clarify that a `[[registry.mirror]]` is associated only with the previous `[[registry]]`. Fixes: containers#1523 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Clarify that a `[[registry.mirror]]` is associated only with the previous `[[registry]]`. Fixes: containers#1523 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
I opened #1525 to clarify the issue in the man pages. |
Clarify that a `[[registry.mirror]]` is associated only with the previous `[[registry]]`. Fixes: containers#1523 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Clarify that a `[[registry.mirror]]` is associated only with the previous `[[registry]]`. Fixes: containers#1523 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
I hope this is the right cri-o repo to report to, if not, please advise.
General Situation
Problem
We cannot specify that a certain mirror is only for certain paths. Thus resulting in a lot of incorrect accesses over the proxies.
Pratical example
The following configuration is taken from a sample kubernetes cluster:
As you can see there are 2 quayio mirrors and 2 dockerhub mirrors. We plan to add 3 mirrors per official source for redundancy reasons. Thus per pull request cri-o might fall through 3 incorrect mirrors and then finally access the correct one.
Improvement
We suggest to add a new field,
prefix
to the mirror list:This way only the mirrors with the right prefix would be contacted.
The text was updated successfully, but these errors were encountered: