-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
CoreDNS issue with minikube when using podman rootless driver #18978
Comments
I have the same problem |
Restarting minikube helped me. This error is reproduced consistently after the first launch.
podman info
|
I am seeing the same thing on Fedora 39. Minikube v1.33.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Happened?
Tested on macOS
Sonoma 14.4.1
Darwin Kernel Version 23.4.0 x86_64
minikube start --addons=ingress --driver=podman --container-runtime=containerd
minikube v1.33.1 on Darwin 14.4.1
Followed the directions at https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/ and it works with podman in rootful mode. When using the podman driver in rootless mode accessing the ingress through minikube tunnel will timeout. It seems that DNS in the ingress-nginx-controller pod is not working which causes nginx to return a 504 timeout.
Also tested using a busybox pod and found the same DNS issue.
CoreDNS logs when running in rootless mode
CoreDNS logs when running in rootful mode - working
Attach the log file
log.txt
Operating System
macOS (Default)
Driver
Podman
The text was updated successfully, but these errors were encountered: