Open sm4sh1k opened 3 years ago
Currently I have the same problem
I am facing similar issues on Mac with the hyperkit driver
Same here with VirtualBox backend
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Same here with Docker
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
I'm not sure what exactly is causing this issue, I would love someone to take a closer look.
I have the same problem PS C:\Windows\system32> minikube.exe tunnel Status: machine: minikube pid: 7464 route: 10.96.0.0/12 -> 172.20.126.198 minikube: Running services: [] errors: minikube: no errors router: error adding route: ·������ʧ��: �����Ѵ��ڡ�
, 3 loadbalancer emulator: no errors
run minikube tunnel
in separate terminal window
Change windows language to en-US will solve this problem. Currently, minikube adds/checks route by compare route
command's output, which will changes based on system language.
We need a better way to examine the execution status of route
command.
seems like an easy fix, I would accept any PR that fixes this relying on English text for the tunnel command
I'd love to take this up but had a hard time figuring out the part introducing the reliance on English text, could you help a bit on this front @medyagh ?
I'll give this issue a try, downloading Windows 11 Russian ISO file.
Minikube tunnel is not working on Windows because of minikube can not recognize the correct answer (or status code) of the route command.
Steps to reproduce the issue:
Full output of failed command:
The first time the route is successfully created, command route ADD 10.96.0.0 MASK 255.240.0.0 192.168.198.128 returns OK (on russian). All next tries to add a route are ended with error The route exists (on russian too). So, in spite of route is created minikube thinks that is not and endlessly tries to create it again and again.