(Solved) failure when minikube enable ingress #16828
Labels
addon/ingress
kind/support
Categorizes issue or PR as a support question.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Comments
ongiant
changed the title
I don't think this is the root cause because when I use command |
|
I believe it's your proxy flags that's causing |
Your method worked : minikube start details
But
this is partial log of the second method's result:
And I used So It looks more like a problem with the network proxy? |
|
What do you get if you run |
spowelljr
added
kind/support
dig registry.k8s.io
In minikube, the output is:
|
|
So the DNS is resolving fine, are you behind a firewall perhaps? Does running the |
My host does't have firewall like UFW. And I can use docker to pull the images hinting in
|
|
I still failed after upgrading minikube to v1.31.1...... Some new findings:
|
Cause & SolutionCauseThe cause is that image cannot be pulled. It works well after I change the image registry. Solutionminikube version: Note:
This is my modified
If you use the Reference
|
QuestionI believe that if I have correctly set up the network for my local machine and Minikube, I should not encounter issues with pulling images. Then, I have some questions:
|
ongiant
changed the title
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
k8s-ci-robot
added
lifecycle/rotten
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
|
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
What Happened?
when I try to enable ingress addon, but it fails.
Command for reproducing the issue:
console output:
console output details
I notice that 'This container is having trouble accessing https://registry.k8s.io ' in above output logs, but I have set proxy for minikube, and referring to this official documentation (I adopted the regular install scheme), I configured a proxy for Docker daemon on my local machine, and it is working properly, so I can't understand this hint.
Then I input
minikube addons enable ingress --profile polar, the output is:Then I try to debug, there are some commands and outputs:
1:
kubectl get pods -A
2:
kubectl describe pod -n ingress-nginx ingress-nginx-controller-6cc5ccb977-26nj7
3: my docker version on my local machine:
docker version
4: In the end, I noticed this sentence in the official documentation of minikube:
It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts.，** What does 'two node' mean here?**After using
minikube node list -p polarcommand,The results indicate that there is just a single node:
Attach the log file
minikube logs --file=logs.txt --profile polar:logs.txt
Operating System
Manjaro Linux
Driver
Docker
update 1:2023-07-10 20:40
I guess that this problem only happens on the
ingress-nginxaddon, because I can enable other addons maintained byKubernetes. Especially,metrics-serveraddon'sDEFAULT REGISTRYis same asingress, both areregistry.k8s.io. see :The text was updated successfully, but these errors were encountered: