Closed nnzv closed 4 months ago
Also, please take a look at the /etc/resolv.conf
file.
ssh -i $(minikube ssh-key) docker@$(minikube ip) "cat /etc/resolv.conf"
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 1.1.1.1
nameserver 8.8.8.8
nameserver 1.0.0.1
# Too many DNS servers configured, the following entries may be ignored.
nameserver 8.8.4.4
nameserver 2606:4700:4700::1111
nameserver 2001:4860:4860::8888
nameserver 2606:4700:4700::1001
nameserver 2001:4860:4860::8844
search .
Fixed it in a weird way by suggesting a fix in another issue https://github.com/kubernetes/minikube/issues/18905#issuecomment-2113954272. Turns out, using containerd did the trick. Didn't realize that earlier, assumed it was already the default, not Docker. Closing the issue now.
/close
@nnzv: Closing this issue.
What Happened?
When attempting to start Minikube with the
kvm2
driver and using the Calico CNI (--cni calico
), there are consistent issues encountered during the image pulling process. The errors indicate a network unreachable problem when trying to pull thecalico/cni:v3.27.3
image from Docker Hub.To reproduce the issue, simply execute the command
minikube start --driver=kvm2 --cni calico
to initiate Minikube with the KVM2 driver and Calico CNI. Observe the process as Minikube attempts to initialize the Kubernetes cluster. The expected behavior is that Minikube should successfully initialize the Kubernetes cluster using the specified driver (kvm2
) and CNI (calico
), without encountering network issues during the image pulling process.However, during the initialization process, Minikube fails to pull the
calico/cni:v3.27.3
image due to a network unreachable error. This failure prevents the successful startup of the Kubernetes cluster. This issue seems to be specific to the combination of thekvm2
driver and the Calico CNI, as it has not been observed with other configurations. Other CNIs might not exhibit this behavior, but further testing is required to confirm.Attach the log file
log.txt
Operating System
Driver