You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, sorry for the german in the logs, the application does this automatically?
I tried running Minikube a second time after I somehow managed to fix this issue once already, I do not remember though how I did it:
minikube start --driver qemu --network socket_vmnet
😄 minikube v1.34.0 auf Darwin 14.6.1 (arm64)
✨ Verwende den Treiber qemu2 basierend auf der Benutzer-Konfiguration
👍 Starte "minikube" primary control-plane Node im "minikube" Cluster
🔥 Erstelle qemu2 VM (CPUs=2, Speicher=6000MB, Disk=20000MB ...- OUTPUT:
ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused
🔥 "minikube" in qemu2 wird gelöscht...
🤦 StartHost fehlgeschlagen, aber es wird noch einmal versucht: creating host: create: creating: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1
🔥 Erstelle qemu2 VM (CPUs=2, Speicher=6000MB, Disk=20000MB ...- OUTPUT:
ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused
😿 Start von qemu2 VM fehlgeschlagen. Das Ausführen von "minikube delete" könnte des Beheben: creating host: create: creating: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1
❌ Terminiere aufgrund von GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: creating: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1
After restarting the socket_vmnet service and running delete --all, it was stuck starting forever:
minikube start --driver qemu --network socket_vmnet
😄 minikube v1.34.0 auf Darwin 14.6.1 (arm64)
✨ Verwende den Treiber qemu2 basierend auf dem existierenden Profil
👍 Starte "minikube" primary control-plane Node im "minikube" Cluster
🔄 Starte existierenden qemu2 VM für "minikube" ...
and after mercy-killing it and trying again, it is stuck in this state ('Aktualisiere' means something like "Refreshing/Updating" in german):
minikube start --driver qemu --network socket_vmnet
😄 minikube v1.34.0 auf Darwin 14.6.1 (arm64)
✨ Verwende den Treiber qemu2 basierend auf dem existierenden Profil
👍 Starte "minikube" primary control-plane Node im "minikube" Cluster
🏃 Aktualisiere den laufenden qemu2 "minikube" VM ...
Attach the log file
First comes the log.txt, next comes running the last command from above with --alsologtostderr
I ran minikube delete --all one more time, and minikube start --driver qemu --network socket_vmnet --alsologtostderr again, and now it works. It might have been a firewall issue but I am not sure. This time I was asked something new and permitted ALL connections, whereas before I permitted just the one which was requested. Could somebody shine some light on this? Is this really just a firewall issue or would that be too easy?
It could very possibly be a firewall issue, we have logic that tries to detect if the firewall is blocking it, seems like it didn't pick it up on your machine though.
if firewall.IsBootpdBlocked(cc) {
if err := firewall.UnblockBootpd(); err != nil {
klog.Warningf("failed unblocking bootpd from firewall: %v", err)
}
}
What Happened?
First of all, sorry for the german in the logs, the application does this automatically?
I tried running Minikube a second time after I somehow managed to fix this issue once already, I do not remember though how I did it:
After restarting the socket_vmnet service and running
delete --all
, it was stuck starting forever:and after mercy-killing it and trying again, it is stuck in this state ('Aktualisiere' means something like "Refreshing/Updating" in german):
Attach the log file
First comes the log.txt, next comes running the last command from above with --alsologtostderr
Operating System
macOS (Default)
Driver
QEMU
The text was updated successfully, but these errors were encountered: