macOS: "Cloud run Debug locally" -> Failed to start minikube: Error while starting minikube. Error: GUEST_PROVISION

[mike-pt]

Type: Bug

Context

• Managed Dependencies: on
• Cloud SDK Version: 431.0.0
• Skaffold Version: v2.3.0
• Minikube Version: 1.30.1

Extension version: 1.21.5 VS Code version: Code 1.78.2 (Universal) (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:44:45.204Z) OS version: Darwin x64 22.4.0 Modes: Sandboxed: No

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|5, 6, 5| |Memory (System)|32.00GB (1.54GB free)| |Process Argv|--crash-reporter-id c7e20d33-f589-47b4-8ded-9d6b1dbed627| |Screen Reader|no| |VM|0%|

A/B Experiments

``` vsliv368cf:30146710 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vstes627:30244334 vslsvsres303:30308271 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 pythondataviewer:30285071 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593:30376534 pythonvs932:30410667 cppdebug:30492333 vsclangdf:30486550 c4g48928:30535728 dsvsc012cf:30540253 pynewext54:30695312 azure-dev_surveyone:30548225 282f8724:30602487 pyind779:30671433 f6dab269:30613381 pythonsymbol12:30671437 2i9eh265:30646982 showlangstatbar:30737416 azdwalk:30721579 pythonms35:30701012 24365598:30736109 pythonfmttext:30731395 pythoncmv:30739700 fixshowwlkth:30730052 pythongtdpath:30739704 ```

[medyagh]

hi there would need the minikube logs or the output minikube logs --file=logs.txt and attach the logs.txt ?

[mike-pt]

@medyagh sorry for taking some time in responding, I was busy with other work, this was filed form the vscode extension there wasn't much more info in the terminal other than that error message, however I tried to run minikube directly and notice its trying to look for dirs that are usually present in Linux (systemd) and also tries to run with sudo which won't work in my case, this is a locked system, even docker is running in "user mode" (via docker desktop)

This is form me manually running /Users/user/Library/Application\ Support/cloud-code/installer/google-cloud-sdk/bin/minikube --driver docker start --alsologtostderr -p cloud-run-dev-internal --keep-context --delete-on-failure

❌  Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: provisioning: Temporary Error: transferring file to machine &{{/Users/miguelc/.minikube/machines/server.pem /etc/docker server.pem 0640 } 0xc000b74060 <nil> 0xc000b3d6d8}: sudo test -d /etc/docker && sudo scp -t /etc/docker && sudo touch -d "2023-05-23 13:18:24.803889716 +0100" /etc/docker/server.pem: Process exited with status 1

The logs command also fails:

/Users/miguelc/Library/Application\ Support/cloud-code/installer/google-cloud-sdk/bin/minikube logs --file=logs.txt
E0523 13:24:32.262581   24776 logs.go:192] command /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.3/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig" failed with error: /bin/bash -c "sudo /var/lib/minikube/binaries/v1.23.3/kubectl describe nodes --kubeconfig=/var/lib/minikube/kubeconfig": Process exited with status 1
stdout:

stderr:
sudo: /var/lib/minikube/binaries/v1.23.3/kubectl: command not found
 output: "\n** stderr ** \nsudo: /var/lib/minikube/binaries/v1.23.3/kubectl: command not found\n\n** /stderr **"

❗  unable to fetch logs for: describe nodes

kubectl is installed via docker but this is looking in /var/lib and also trying to use sudo ...

Probably needs some "if osx" do this... :D

We probably don't need sudo in some case, certainly not kubectl cmds, but for docker dirs, we might, depending on how docker is installed so that is probably ok for most cases just not when folks have a bit more locked down systems.