<p>I use the Google Cloud Code extension on VSCode.
I have a minikube running on my macbook (using the virtualbox driver).</p>
<p>I can run <code>skaffold debug</code> from my terminal just fine; the Helm chart gets deployed, but I haven't done the debugger setup so the breakpoints don't hit (as expected).</p>
<p>I want to use the Cloud Code extension to avoid manually doing the debugger setup.
However, if I run &quot;debug on Kubernetes&quot; in the Cloud Code extension, I get a prompt saying &quot;Docker was found in the path but does not appear to be running. Start Docker to continue&quot;:
<a href="https://i.stack.imgur.com/0HAI0.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0HAI0.png" alt="VSCode prompt asking me to start docker" /></a></p>
<p>If I select &quot;start Docker&quot;, then Docker Desktop will be started, which I want to avoid. It seems to me that Cloud Code needs to do the equivalent of running <code>eval $(minikube -p minikube docker-env)</code> to use the minikube Docker daemon. Is there a setting to get it to do that?</p>

AdrienF
<p>my work around.</p>
<pre><code>ls -l /var/run/docker.sock
# /var/run/docker.sock -&gt; $HOME/.docker/run/docker.sock
sudo rm /var/run/docker.sock

ssh -i ~/.minikube/machines/minikube/id_rsa -L $HOME/.minikube/docker.sock:/var/run/docker.sock docker@$(minikube ip) -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null

sudo ln -s $HOME/.minikube/docker.sock /var/run/docker.sock

if curl -s --unix-socket /var/run/docker.sock http/_ping 2&gt;&amp;1 &gt;/dev/null
then
  echo &quot;Running&quot;
else
  echo &quot;Not running&quot;
fi
# Running
</code></pre>
