kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

add known issue to qemu documentation

pull/15043/head
Steven Powell 2022-09-29 15:51:35 -07:00
parent d5668285d8
commit d6c293d76e
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
site/content/en/docs/drivers/qemu.md
View File

@ -29,10 +29,17 @@ minikube start supports some qemu specific flags:
* Note: while the flag should override the config, if the flag does not take effect try running `minikube delete`.
* MacPorts: if you are installing [minikube](https://ports.macports.org/port/minikube/) and [qemu](https://ports.macports.org/port/qemu/) via MacPorts on a Mac with M1, use the following flag: `--qemu-firmware-path=/opt/local/share/qemu/edk2-aarch64-code.fd`
## Issues
## Known Issues
* [Full list of open 'qemu' driver issues](https://github.com/kubernetes/minikube/labels/co%2Fqemu-driver)
* When using the `user` network (default) the guest uses **only** the first `nameserver` entry in the hosts `/etc/resolv.conf` for DNS lookup.
* If your first `nameserver` entry is a corporate/internal DNS it's likely it will cause an issue.
* If you see the warning `❗ This VM is having trouble accessing https://registry.k8s.io` on `minikube start` you are likely being affected by this.
* This may prevent your cluster from starting entirely and you won't be able to pull remote images.
* If possible, reorder your `/etc/resolv.conf` to have a general `nameserver` entry first (eg. `8.8.8.8`) and reboot your machine.
* More details can be found at: [#15021](https://github.com/kubernetes/minikube/issues/15021)
## Troubleshooting
* Run `minikube start --alsologtostderr -v=4` to debug crashes