-
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
Network Unreachable Error When Pulling calico/cni:v3.27.3 #18907
Comments
Also, please take a look at the
|
Fixed it in a weird way by suggesting a fix in another issue #18905 (comment). 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. 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-sigs/prow repository. |
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
The text was updated successfully, but these errors were encountered: