title: Why does minikube start sometimes hang on mac os High Sierra 10.13.6?
body: <p>I upgraded my mac to version 10.13.6 yesterday, restarted my mac laptop. Now, minikube won't start. Docker Community Edition 18.06.1-ce is running. The logs are below. Can anyone spot what is wrong. How do I debug this more?</p>
  
  <pre><code>$ minikube version
  minikube version: v0.30.0
  
  
  $ minikube update-check
  CurrentVersion: v0.30.0
  LatestVersion: v0.30.0
  
  
  $ minikube start --v=999 --logtostderr   --vm-driver=hyperkit
  W1101 12:02:25.674822   24809 root.go:146] Error reading config file at /Users/user/.minikube/config/config.json: open /Users/user/.minikube/config/config.json: no such file or directory
  I1101 12:02:25.675028   24809 notify.go:121] Checking for updates...
  I1101 12:02:25.971633   24809 start.go:99] Viper configuration:
  Aliases:
  map[string]string{}
  Override:
  map[string]interface {}{"v":"999"}
  PFlags:
  map[string]viper.FlagValue{"apiserver-names":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a460)}, "network-plugin":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a8c0)}, "registry-mirror":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a6e0)}, "vm-driver":viper.pflagValue{flag:(*pflag.Flag)(0xc420367c20)}, "cpus":viper.pflagValue{flag:(*pflag.Flag)(0xc420367d60)}, "disk-size":viper.pflagValue{flag:(*pflag.Flag)(0xc420367e00)}, "feature-gates":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a960)}, "hyperkit-vsock-ports":viper.pflagValue{flag:(*pflag.Flag)(0xc42033ac80)}, "disable-driver-mounts":viper.pflagValue{flag:(*pflag.Flag)(0xc420367ae0)}, "gpu":viper.pflagValue{flag:(*pflag.Flag)(0xc42033ad20)}, "nfs-share":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a140)}, "uuid":viper.pflagValue{flag:(*pflag.Flag)(0xc42033ab40)}, "apiserver-name":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a3c0)}, "cache-images":viper.pflagValue{flag:(*pflag.Flag)(0xc42033aa00)}, "xhyve-disk-driver":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a0a0)}, "dns-domain":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a5a0)}, "docker-opt":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a320)}, "host-only-cidr":viper.pflagValue{flag:(*pflag.Flag)(0xc420367ea0)}, "memory":viper.pflagValue{flag:(*pflag.Flag)(0xc420367cc0)}, "nfs-shares-root":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a1e0)}, "iso-url":viper.pflagValue{flag:(*pflag.Flag)(0xc420367b80)}, "bootstrapper":viper.pflagValue{flag:(*pflag.Flag)(0xc420366fa0)}, "container-runtime":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a780)}, "docker-env":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a280)}, "extra-config":viper.pflagValue{flag:(*pflag.Flag)(0xc42033aaa0)}, "insecure-registry":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a640)}, "apiserver-ips":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a500)}, "keep-context":viper.pflagValue{flag:(*pflag.Flag)(0xc420367900)}, "kvm-network":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a000)}, "mount":viper.pflagValue{flag:(*pflag.Flag)(0xc4203679a0)}, "mount-string":viper.pflagValue{flag:(*pflag.Flag)(0xc420367a40)}, "profile":viper.pflagValue{flag:(*pflag.Flag)(0xc420366f00)}, "hyperkit-vpnkit-sock":viper.pflagValue{flag:(*pflag.Flag)(0xc42033abe0)}, "hyperv-virtual-switch":viper.pflagValue{flag:(*pflag.Flag)(0xc420367f40)}, "kubernetes-version":viper.pflagValue{flag:(*pflag.Flag)(0xc42033a820)}}
  Env:
  map[string]string{}
  Key/Value Store:
  map[string]interface {}{}
  Config:
  map[string]interface {}{}
  Defaults:
  map[string]interface {}{"log_dir":"", "reminderwaitperiodinhours":24, "wantnonedriverwarning":true, "showdriverdeprecationnotification":true, "showbootstrapperdeprecationnotification":true, "v":"0", "alsologtostderr":"false", "wantupdatenotification":true, "wantreporterror":false, "wantreporterrorprompt":true, "wantkubectldownloadmsg":true}
  Starting local Kubernetes v1.10.0 cluster...
  Starting VM...
  I1101 12:02:25.972050   24809 utils.go:100] retry loop 0
  I1101 12:02:25.972089   24809 cluster.go:73] Skipping create...Using existing machine configuration
  Found binary path at /usr/local/bin/docker-machine-driver-hyperkit
  Launching plugin server for driver hyperkit
  Plugin server listening at address 127.0.0.1:56021
  () Calling .GetVersion
  Using API Version  1
  () Calling .SetConfigRaw
  () Calling .GetMachineName
  (minikube) Calling .GetState
  I1101 12:02:26.011670   24809 cluster.go:82] Machine state:  Stopped
  (minikube) Calling .Start
  (minikube) Using UUID fa403fab-dbb5-11e8-812b-8c859058d45f
  (minikube) Generated MAC 86:5b:e6:33:fc:a1
  (minikube) Starting with cmdline: loglevel=3 user=docker console=ttyS0 console=tty0 noembed nomodeset norestore waitusb=10 systemd.legacy_systemd_cgroup_controller=yes base host=minikube
  (minikube) Calling .GetConfigRaw
  (minikube) Calling .DriverName
  Waiting for SSH to be available...
  Getting to WaitForSSH function...
  (minikube) Calling .GetSSHHostname
  (minikube) Calling .GetSSHPort
  (minikube) Calling .GetSSHKeyPath
  (minikube) Calling .GetSSHKeyPath
  (minikube) Calling .GetSSHUsername
  Using SSH client type: native
  &amp;{{{&lt;nil&gt; 0 [] [] []} docker [0x140f940] 0x140f910  [] 0s} 192.168.64.4 22 &lt;nil&gt; &lt;nil&gt;}
  About to run SSH command:
  exit 0
  
  Error dialing TCP: dial tcp 192.168.64.4:22: connect: operation timed out
  Error dialing TCP: dial tcp 192.168.64.4:22: connect: operation timed out
  Error dialing TCP: dial tcp 192.168.64.4:22: connect: operation timed out
  </code></pre>
  
  <p>Update: I created an a json file containing {} at /Users/user/.minikube/config/config.json but it still hangs.</p>
  
  <p>I printed the process tree and found that the child process</p>
  
  <pre><code>/usr/local/bin/docker-machine-driver-hyperkit
  </code></pre>
  
  <p>is the one hanging.</p>