Can not pull access any external resource with hyperkit driver #5336
Comments
|
I don’t yet have a clear way to replicate this issue. Do you mind adding some additional details? Here is additional information that would be helpful:
My apologies for minikube not working well for you yet with hyperkit. I think we can get to the bottom of this issue quickly. This seems to indicate that the built-in hyperkit DNS proxy isn't working:
|
tstromberg
added
co/hyperkit
|
Thank you for such a quick response! Yes, it looks like it does not works with external addresses. Here are all outputs: $ /usr/local/bin/docker-machine-driver-hyperkit version
version: v1.3.1
commit: ca60a424ce69a4d79f502650199ca2b52f29e631$ hyperkit -version
hyperkit: v0.20190201-11-gc0dd46
Homepage: https://github.com/docker/hyperkit
License: BSDminikube start --vm-driver=hyperkit$ minikube start --vm-driver=hyperkit
😄 minikube v1.3.1 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.15.2 on Docker 18.09.8 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube" |
|
OK, nothing unusual about your configuration as far as I can see yet. There likely isn't any need to set Do you mind sharing the output of:
|
|
After creation another minikube machine with If you need the test, just let me know, otherwise you can close the issue. Thank you for the help! |
$ minikube delete -p dev
🔥 Deleting "dev" in hyperkit ...
💔 The "dev" cluster has been deleted.
$ minikube start --vm-driver=hyperkit -p dev
😄 [dev] minikube v1.3.1 on Darwin 10.14.6
🏃 Using the running hyperkit "dev" VM ...
⌛ Waiting for the host to be provisioned ...
🐳 Preparing Kubernetes v1.15.2 on Docker 18.09.8 ...
🔄 Relaunching Kubernetes using kubeadm ...
⌛ Waiting for: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "dev"
$ minikube ssh -p dev ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=53 time=41.225 ms
$ minikube ssh -p dev nslookup google.com 8.8.8.8
Server: 8.8.8.8
Address 1: 8.8.8.8 dns.google
Name: google.com
Address 1: 172.217.168.174 mad07s10-in-f14.1e100.net
Address 2: 2a00:1450:4003:809::200e mad08s05-in-x0e.1e100.net
$ ps -afe | egrep -i 'hyperkit|InternetSharing'
0 69938 1 0 9:23am ?? 0:00.79 /usr/libexec/InternetSharing
501 79005 79001 0 12:25pm ?? 57:42.39 com.docker.hyperkit -A -u -F vms/0/hyperkit.pid -c 10 -m 6144M -s 0:0,hostbridge -s 31,lpc -s 1:0,virtio-vpnkit,path=vpnkit.eth.sock,uuid=85cedf19-2c30-42f6-a55b-cc542bb91825 -U c4493641-002d-4252-923c-f65f5956e74a -s 2:0,ahci-hd,/Users/mike/Library/Containers/com.docker.docker/Data/vms/0/Docker.raw -s 3,virtio-sock,guest_cid=3,path=vms/0,guest_forwards=2376;1525 -s 4,ahci-cd,/Applications/Docker.app/Contents/Resources/linuxkit/docker-desktop.iso -s 5,ahci-cd,vms/0/config.iso -s 6,ahci-cd,/Applications/Docker.app/Contents/Resources/linuxkit/docker.iso -s 7,virtio-rnd -l com1,autopty=vms/0/tty,asl -f bootrom,/Applications/Docker.app/Contents/Resources/uefi/UEFI.fd,,
0 438 1 0 9:43am ttys011 3:26.61 /usr/local/bin/hyperkit -A -u -F /Users/mike/.minikube/machines/dev/hyperkit.pid -c 2 -m 2000M -s 0:0,hostbridge -s 31,lpc -s 1:0,virtio-net -U 043dbca8-d85e-11e9-b896-acde48001122 -s 2:0,virtio-blk,/Users/mike/.minikube/machines/dev/dev.rawdisk -s 3,ahci-cd,/Users/mike/.minikube/machines/dev/boot2docker.iso -s 4,virtio-rnd -l com1,autopty=/Users/mike/.minikube/machines/dev/tty,log=/Users/mike/.minikube/machines/dev/console-ring -f kexec,/Users/mike/.minikube/machines/dev/bzimage,/Users/mike/.minikube/machines/dev/initrd,earlyprintk=serial loglevel=3 user=docker console=ttyS0 console=tty0 noembed nomodeset norestore waitusb=10 systemd.legacy_systemd_cgroup_controller=yes base host=dev
501 9726 96089 0 9:51am ttys011 0:00.00 egrep -i hyperkit|InternetSharing
sudo lsof -i :53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dnsmasq 55 nobody 4u IPv4 0xe69bc567e18dbecb 0t0 UDP localhost:domain
dnsmasq 55 nobody 5u IPv4 0xe69bc567edaf5fcb 0t0 TCP localhost:domain (LISTEN)
dnsmasq 55 nobody 6u IPv6 0xe69bc567e18dcf1b 0t0 UDP localhost:domain
dnsmasq 55 nobody 7u IPv6 0xe69bc567edafa2cb 0t0 TCP localhost:domain (LISTEN)
dnsmasq 55 nobody 8u IPv6 0xe69bc567e18dd1d3 0t0 UDP localhost:domain
dnsmasq 55 nobody 9u IPv6 0xe69bc567edaf9d0b 0t0 TCP localhost:domain (LISTEN)reproduced the issue (with the same profile got the same). Looks like it dies after the second run. With VirtualBox provider everything still works. |
|
Thank you for the additional info. I'd be willing to bet that hyperkit's DNS server is conflicting with dnsmasq. This is a known issue: https://minikube.sigs.k8s.io/docs/reference/drivers/hyperkit/#Issues Here's some background: #3036 Can you try turning off dnsmasq to confirm? Alternatively, it should be possible to change dnsmasq to bind only to a certain IP, such as 127.0.0.1, so that it does not conflict. Please let me know how it goes. |
|
Thank you @tstromberg for the link! It helps, will provide the steps to fix below. Upgraded dnsmasq from 2.7.9 to 2.8.0 with $ cat /usr/local/etc/dnsmasq.conf
address=/.loc/127.0.0.1So I run minikube delete && rm -rf ~/.minikube ~/.kube
sudo rm /var/db/dhcpd_leases
mkdir -p /usr/local/etc/dnsmasq.d/minikube
echo 'listen-address=192.168.64.1' > /usr/local/etc/dnsmasq.d/minikube/minikube.conf
sudo launchctl stop homebrew.mxcl.dnsmasq
sudo launchctl start homebrew.mxcl.dnsmasqIDK which exactly step helps, but hope that this chunk of code may helps somebody. |
|
Excellent. I'm glad you were able to get this worked out! |
|
IP address of minikube host may vary, so use your |
|
This did not help me....I am moving to |
This with after entire re-install of the cluster. With VirtualBox driver everything works well.
Do not have any proxy on the host system, but already tried the solution from here with lo luck.
The exact command to reproduce the issue:
export NO_PROXY=localhost,127.0.0.1,10.96.0.0/12,192.168.0.0/16 minikube start --vm-driver=hyperkit$ minikube ssh _ _ _ _ ( ) ( ) ___ ___ (_) ___ (_)| |/') _ _ | |_ __ /' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\ | ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/ (_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____) $ curl google.com curl: (6) Could not resolve host: google.com $ nslookup google.com Server: 192.168.64.1 Address 1: 192.168.64.1 nslookup: can't resolve 'google.com'The output of the
minikube logscommand:The operating system version:
Mac Os 10.14.6
minikube 1.3.1
The text was updated successfully, but these errors were encountered: