Open balopat opened 5 years ago
I wonder if this is still an issue 🤔
I'm going to close this one. Not sure this is still an issue. Since then, Skaffold now fails on a failed minikube docker-env
I have the same problem today
PS C:\windows\system32> minikube version minikube version: v1.12.3 commit: 2243b4b97c131e3244c5f014faedca0d846599f5-dirty
minikube start --vm-driver=hyperv
skaffold build -p dev creating runner: creating builder: getting docker client: getting minikube env: running [minikube docker-env --shell none]
works if I launch skaffold from a "Administrator Powershell"
@gsquared94 this seems a motivator to make our KubeContext into a proper struct and move the minikube docker-env
into the minikube detection. That way if minikube docker-env
fails, then we downgrade the a normal non-local cluster KubeContext. WDYT?
Expected behavior
When skaffold detects that minikube's docker daemon can't be resolved (as the warning shows as well) it should either:
build.local.push = false
is setupbuild.local.push =true
when it is not setupActual behavior
Skaffold fails to find the minikube docker daemon and hence creates a deployment inside minikube that relies on a non-existent image (as it is not pushed):
Information
Steps to reproduce the behavior
Run Skaffold in a non-admin powershell window against a hyperv minikube instance (that needs admin rights):
skaffold dev