Minikube commands trigger Docker context error.

[albertalvin8080]

What Happened?

When I run any minikube command, it's logged that the "default" Docker CLI context cannot be found. The thing is, I'm not trying to use docker. It happens even when Docker is not running.

For example, when i use minikube status, the output is:

W0506 23:45:30.171668 800 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\Albert.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
minikube
type: Control Plane
host: Stopped
kubelet: Stopped
apiserver: Stopped
kubeconfig: Stopped

As you can see, the status command is executed normaly. But the docker error is always triggered before the actual execution of the command.

For minikube config get vm-driver command:

W0506 23:59:03.135165 10532 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\Albert.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
hyperv

Even if it's still harmless (so far), I'd like to understand why it happens.

Operating System

Windows

Driver

N/A