minikube 0.30.0 DNS not working on CentOS 7 with Docker 18.06.1-ce and vm-driver=none
what is nix
I am experimenting with minikube for learning purposes, on a CentOS 7 Linux machine with Docker 18.06.010ce installed
I installed minikube using
minikube start --vm-driver=none"
I deployed a few applications but only to discover they couldn't talk to each other using their hostnames.
I deleted minikube using
I re-installed minikube using
minikube start --vm-driver=none
I then followed the instructions under "Debugging DNS Resolution" (https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/) but only to find out that the DNS system was not functional
More precisely, I run:
kubectl create -f https://k8s.io/examples/admin/dns/busybox.yaml
# kubectl exec -ti busybox -- nslookup kubernetes.default Server: 10.96.0.10 Address 1: 10.96.0.10 nslookup: can't resolve 'kubernetes.default' command terminated with exit code 1
# kubectl exec busybox cat /etc/resolv.conf nameserver 10.96.0.10 search default.svc.cluster.local svc.cluster.local cluster.local contabo.host options ndots:5
# kubectl get pods --namespace=kube-system -l k8s-app=kube-dns NAME READY STATUS RESTARTS AGE coredns-c4cffd6dc-dqtbt 1/1 Running 1 4m kube-dns-86f4d74b45-tr8vc 2/3 Running 5 4m
surprisingly both kube-dns and coredns are running should this be a concern?
I have looked for a solution anywhere without success step 2 always returns error
I simply cannot accept that something so simple has become such a huge trouble for me Please assist
Mine is working with coredns enabled and kube-dns disabled.
C02W84XMHTD5:ucp iahmad$ minikube addons list - addon-manager: enabled - coredns: enabled - dashboard: enabled - default-storageclass: enabled - efk: disabled - freshpod: disabled - heapster: disabled - ingress: disabled - kube-dns: disabled - metrics-server: disabled - nvidia-driver-installer: disabled - nvidia-gpu-device-plugin: disabled - registry: disabled - registry-creds: disabled - storage-provisioner: enabled
you may disable the kube-dns:
minikube addons disable kube-dns
Mine devre dışı etkin coredns ve kube-dns ile çalışıyor. C02W84XMHTD5:ucp iahmad$ minikube addons list - addon-manager: enabled - coredns: enabled I've added a message to the top of the Installing Minikube on Linux guide referencing @tstromberg 's cautionary MD file to indicate that developers should not use the --vm-driver=none option on a laptop or PC running Linux, a section on checking for existing minikube and kubectl configuration files and binaries, and expected output for the
Please note the output of
kube-dns pod below, it has only 2 of 3 containers running.
kube-dns-86f4d74b45-tr8vc 2/3 Running 5 4m
The last time I encountered this was when Docker's default
FORWARD policy was
DROP. Changing it to
ACCEPT using below fixed the problem for me.
iptables -P FORWARD ACCEPT
It might be other things too, please check the pod logs.
mkube: Booting VM. mkube: docker-engine x86_64 17.05.0.ce-1.el7.centos @dockerrepo 70 M mkube: --> Processing Dependency: libvirt-daemon-driver-qemu = 4.5.0-10.el7 for package: mkube: libgpg-error i686 1.12-3.el7 centos7 87 k mkube: Public key for docker-ce-18.06.1.ce-3.el7.x86_64.rpm is not installed. Minikube version 0.19.1 Environment: OS MAC OS 10.11.4 VM Driver virtualbox ISO version minikube-1.13.1-3.iso: Install tools: Others: What happened: If I start minikube with --dns-domain the dns entries that are registered are still regi
After deleting /etc/kubernetes and /var/lib/kubelet and /var/lig/kubeadm.yaml and restarting minikube I can now successfully reproduce the DNS resolution debugging steps (https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/)
I bet some stale settings had persisted among minikube start/top iterations leading to inconsistent configuration.
DevOps; Using Packer; Using Ansible-Galaxy; Using Vagrant; Using Ansible; Using Docker; Using Kubernetes; Using Openshift; Using Git; ToDo; Misc; Test In this blog post tutorial, we will learn, how to install a single node Kubernetes cluster via minikube. We will install minikube on CentOS 7 natively without the need for any virtual machine layer. This post is inspired by the… Read More Kubernetes (1) – Installing Minikube on CentOS
It is also worth mentioning that DNS resolution was lost after restarting the iptables.
I suspect this is iptables rules related, some rule ie being put by minikube and as it gets lost as part of iptables restart the problem re-appears
Bug Tracker, https://github.com/NixOS/nixpkgs/issues actor-framework-0.15.7 docker-18.06.1-ce docker-gc-b0cc52aa3da2e2ac0080794e0be6e674b1f063fc gfxtablet-uinput-driver-1.4 perl5.22.4-Net-DNS-Resolver-Programmable-0.009 perl5.22.4-VM-EC2-Security-CredentialCache-0.25 sudo /usr/local/bin/minikube start --vm-driver=none --use-vendored-driver --alsologtostderr --v=3 to start local kube as mentioned here What you expected to happen : We expected to have running kubernetes cluster
I managed to resolve the problem by re-installing Minikube after deleting all state files under /etc and /var/lib, but forgot to update.
This can be now closed.
How to resolve Kubernetes DNS issues when trying to install Weave Cloud Agents for Minikube. However none of them resolved my issue. minikube v1.7.2 on Centos 7.7.1908 Docker 19.03.5 vm-driver=virtualbox Connecting minikube 0.30.0 DNS not working on CentOS 7 with Docker 18.06.1-ce and vm-driver= tstromberg changed the title DNS not working for pod in cluster on minikube 0.18.0 virtualbox: external DNS does not work within guest VM Sep 19, 2018 This comment has been minimized. Sign in to view
minikube 0.30.0 DNS not working on CentOS 7 with Docker 18.06.1-ce and I installed minikube using minikube start --vm-driver=none' I deployed a few I enabled the kube-dns addon. I did minikube stop && minikube delete. I upgrade k8s to v1.10.0 and started minikube again. Addon is still enabled but no pods are there. I'm unable to enable the addon again. $ minikube addons disable kube-dns minikube is not currently running so the service cannot be accessed (same for enable)
Kubernetes Minikube on Windows Pod failed to pull image minikube 0.30.0 DNS not working on CentOS 7 with Docker 18.06.1-ce and vm-driver=none using minikube start --vm-driver=none' I deployed a few applications but only to Note: If you are behind a web proxy, you need to pass this information to the minikube start command: shell https_proxy=<my proxy> minikube start --docker-env http_proxy=<my proxy> --docker-env https_proxy=<my proxy> --docker-env no_proxy=192.168.99.0/24 Unfortunately, setting the environment variables alone does not work. Minikube also creates
I need your help with this error: ORA-00907 on Check CONSTRAINT Query: CREATE TABLE S_NEWS. minikube 0.30.0 DNS not working on CentOS 7 with Docker 18.06.1-ce and vm-driver=none 2012-09-02 in dns Confirm Installation To confirm successful installation of both a hypervisor and Minikube, you can run the following command to start up a local Kubernetes cluster: Note: For setting the --driver with minikube start, enter the name of the hypervisor you installed in lowercase letters where <driver_name> is mentioned below. A full list of --driver values is available in specifying the VM driver
- # iptables --list Chain KUBE-SERVICES (1 references) target prot opt source destination REJECT udp -- 0.0.0.0/0 10.96.0.10 /* kube-system/kube-dns:dns has no endpoints / udp dpt:53 reject-with icmp-port-unreachable REJECT tcp -- 0.0.0.0/0 10.96.0.10 / kube-system/kube-dns:dns-tcp has no endpoints / tcp dpt:53 reject-with icmp-port-unreachable REJECT tcp -- 0.0.0.0/0 10.98.123.7 / kube-system/kubernetes-dashboard: has no endpoints */ tcp dpt:80 reject-with icmp-port-unreachable
- even worse, this is not always happening sometimes I only see
Chain KUBE-SERVICES (1 references) target prot opt source destination REJECT tcp -- 0.0.0.0/0 10.98.123.7 /* kube-system/kubernetes-dashboard: has no endpoints */ tcp dpt:80 reject-with icmp-port-unreachable
# kubectl logs --namespace=kube-system pod/kube-dns-86f4d74b45-XXXXX -c kubedns ... E1025 12:27:58.105775 1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:150: Failed to list *v1.Service: Get https://10.96.0.1:443/api/v1/services?resourceVersion=0: dial tcp 10.96.0.1:443: getsockopt: connection refused