-
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
minikube start -> panic: runtime error: invalid memory address or nil pointer dereference #3555
Comments
Deleted ~/.minikube folder, rebooted, and it started. Not sure what it was, but I'll call it solved. |
I ran into this today:
The strace output didn't yield any obvious problems to me, other than ssh complaining about something or another. Using I0501 11:46:17.451602 70519 ssh_runner.go:101] SSH: sudo mkdir -p /etc/kubernetes/addons
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x117f24a] Nothing suspicious entries in dmesg either. I'll dig a little further. |
The problem disappeared before I had a proper chance to debug it. As far as I can tell, it's just scp'ing data from an in memory []byte{} to scp, so I'm not exactly sure why it would crash. Searching around, other folks have hit a similar panic, and it's possible that it's related to negative or conflicting reads. It feels like a race condition, but I was able to replicate it so many times that I'm not sure. |
Increasing priority, since @medyagh also ran into this today. |
I tried deleting the
and here is my minikube logs
|
Hmm, wonder if I missed a dependency when I removed the templating from the default target... |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
Minikube version (use
minikube version
): minikube version: v0.33.0cat ~/.minikube/machines/minikube/config.json | grep DriverName
): hypervcat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): file://C:/Users/.../.minikube/cache/iso/minikube-v0.33.0.isominikube-windows-amd64
from github releases, renamed tominikube.exe
and added to pathdocker --version
: Docker version 18.09.1, build 4c52b90The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
What happened:
ran
minikube.exe start --vm-driver="hyperv" --hyperv-virtual-switch="minikube" --alsologtostderr
got this:
Then ran this:
minikube status
got this:
What you expected to happen: Minikube to startup correctly
How to reproduce it (as minimally and precisely as possible):
Output of
minikube logs
(if applicable):Anything else do we need to know: Minikube 0.31.0 worked, this happened right after upgrade.
The text was updated successfully, but these errors were encountered: