-
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 (qemu2) failes to start with "failed to get IP address" #15960
Comments
Some kind of compatibility issue with socket_vmnet, it only lists one DHCP entry coming from "colima"
|
I'm not sure what is going on yet but I am also experiencing this issue, which seems to be a regression as compared to versions before minikube I'll post logs but, in summary, I'm unable to successfully start a minikube cluster when using Here are my machine details: ❯ macchina ─╯
,MMMM. Host - <REMOVED>
.MMMMMM Machine - Mac13,2
MMMMM, Kernel - 22.4.0
.;MMMMM:' MMMMMMMMMM;. OS - macOS 13.3.1 Ventura
MMMMMMMMMMMMNWMMMMMMMMMMM: DE - Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMWM. WM - Quartz Compositor
MMMMMMMMMMMMMMMMMMMMMMMMM. Packages - 263 (Homebrew)
;MMMMMMMMMMMMMMMMMMMMMMMM: Terminal - iTerm2 (Version 3.4.19)
:MMMMMMMMMMMMMMMMMMMMMMMM: Shell - zsh
.MMMMMMMMMMMMMMMMMMMMMMMMM. Uptime - 3d 5h 49m
MMMMMMMMMMMMMMMMMMMMMMMMMMM. CPU - Apple M1 Ultra (20)
.MMMMMMMMMMMMMMMMMMMMMMMMMM. Resolution - 5120x2880@60fps (as 2560x1440)
MMMMMMMMMMMMMMMMMMMMMMMM 5120x2880@60fps (as 2560x1440)
;MMMMMMMMMMMMMMMMMMMM. Brightness - 100%
.MMMM,. .MMMM,. CPU Load - 18%
Memory - 60.2 GB/134.2 GB Minikube version is: minikube version: v1.30.1
commit: 08896fd1dc362c097c925146c4a0d0dac715ace0 I will do more testing tomorrow. |
FWIW, here are my logs from today's latest attempt to start minikube with minikube_logs_246a8c5e046f473e09b808593858b4737e8d9296_0.log ❯ minikube config view
- container-runtime: containerd
- cpus: 6
- driver: qemu2
- memory: 16384 ❯ minikube start --network socket_vmnet
😄 minikube v1.30.1 on Darwin 13.3.1 (arm64)
✨ Using the qemu2 driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
💾 Downloading Kubernetes v1.26.3 preload ...
> preloaded-images-k8s-v18-v1...: 358.98 MiB / 358.98 MiB 100.00% 44.94 M
🔥 Creating qemu2 VM (CPUs=6, Memory=16384MB, Disk=20000MB) ...
🔥 Deleting "minikube" in qemu2 ...
🤦 StartHost failed, but will try again: creating host: create: creating: IP address never found in dhcp leases file: failed to get IP address: could not find an IP address for 5e:40:c0:5c:ab:86
🔥 Creating qemu2 VM (CPUs=6, Memory=16384MB, Disk=20000MB) ...
😿 Failed to start qemu2 VM. Running "minikube delete" may fix it: creating host: create: creating: IP address never found in dhcp leases file: failed to get IP address: could not find an IP address for 42:74:86:6:b8:92
❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: creating: IP address never found in dhcp leases file: failed to get IP address: could not find an IP address for 42:74:86:6:b8:92
╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯ I'm using ❯ sudo brew services info socket_vmnet
socket_vmnet (homebrew.mxcl.socket_vmnet)
Running: ✔
Loaded: ✔
Schedulable: ✘
User: root
PID: 743 I've also tried different values of |
Just tried this with newly released minikube v1.31.0. Still busted on amd64 (might be working as 1.30.x on arm64!) |
Still busted on arm64, also. As several folks have mentioned, the fix for me on both amd64 and arm64 is to restart socket_vmnet via minikube delete
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/libexec/bootpd
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock /usr/libexec/bootpd This workaround works for me 100% of the time. |
minikube v1.31.0 should unblock the firewall if it detects it's being blocked.
But restarting socket_vmnet via |
I can't get it to run on amd64, even with the ownership on
|
Did you run |
@mprimeaux Yep. Here's the status:
|
@torenware There are days I wish I were on a beach :) Interestingly enough, I had this very scenario happen when I was in an airport last week. Turns our, the captured network was preventing my VM from obtaining a DHCP address. By chance, are you on a captured network? |
File:
Nope. Plain vanilla wifi, no fancy stuff going on. |
I also have this issue, Macbook Pro 16" 2019 Intel running Ventura 13.5. |
I am having this exact same issue as well. Has a fix been found? |
I think I have found a workaround + there is a code change needed I've just created. First you start colima, make sure it works, then socket_vmnet. Also make sure to define proper firewall rules for bridge created. What is more, you're going to need to edit the After editing a profile for colima/preparing it (containerd, sshfs):
I have also made sure I've added proper anchor and pfctl rules for the bridge created as mentioned above and made sure other firewalls are not blocking bootpd (system and apps). Basically this needs to appear (in my case) - username cannot be overriden hence the initial PR.
Initial PR: 7e9f3a6 PR has been updated to cover the SSHPort discovery of colima machine and its ssh_config. |
It was not intended to start two VMs, so it seems strange to have both colima and minikube qemu2 running. Overriding the user name is something that could be considered for all drivers, but it is not needed for the kic image. For colima, it normally starts k3s when you run it with
For lima, it simply runs
|
Agreed that it is not common, I had to run vmnet separately having those 2 machines and I do not run k3s there with colima, however I was able to obtain the minikube address with the usage of localhost and MAC address in this setup. I am generally thinking about moving this towards lima driver (or dig into qemu2 even deeper) and it's just how I started: see the ip below:
|
Agreed that 2 VMs are not intended to start, I changed the course and worked with dhcp leases a little bit, created proper bridge with vmnet and used lima without colima, now it looks correct, getting myself to speed with the project, can't wait to add more nodes λ ~/ minikube profile list λ ~/ kubectl get po -A λ ~/ k get no If I am able to find some free time I will see if this issue can be somehow addressed - need to make sure I have full understanding of the setup. Starts getting proper shapes. Started with: |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
@mprimeaux wrote:
This worked for me once yesterday, and I was so happy, but today it fails again: GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: creating: ip not found: failed to get IP address: could not find an IP address for 66:17:20:72:c8:65
In my case, the firewall does not seem to be the problem because |
I managed to get bootpd running by doing |
What Happened?
Minikube fails to start:
Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: IP address never found in dhcp leases file: failed to get IP address: could not find an IP address for xx:xx:xx:xx:xx:xx
Attach the log file
minikube-logs.txt
minikube_logs_e4032c57df89461a76cf8ea248c98ea6558dccb1_0.log
Operating System
macOS (Default)
Driver
QEMU
The text was updated successfully, but these errors were encountered: