GoogleContainerTools / GoogleContainerTools/skaffold
Allow using host docker daemon instead of minikube's
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
Description
### Expected behavior
I want to be able to use my host docker daemon to build my docker images, instead of minikube's docker daemon.
For more context, I want to use my host docker daemon and then push to Minikube's registry addon, as the minikube cluster is running with constrained resources, so building my docker images in minikube takes an extremely long time. It's quicker for me to build on my host, and then push the resulting image into minikube's registry.
Currently, this appears impossible with Skaffold as I can't make it _not_ use minikube's docker daemon.
### Actual behavior
No matter what I try, skaffold will always detect minikube and use its docker daemon intead of my host.
This is confirmed by running `skaffold dev -v info` and the output always shows:
```
[...]
INFO[0000] Using kubectl context: minikube
INFO[0000] Using minikube docker daemon at tcp://192.168.99.112:2376
[...]
```
I thought setting `--detect-minikube=false` would resolve this, but it does not.
### Information
- Skaffold version: v1.19.0
- Operating system: MacOS (running Minikube with the Virtualbox driver)
### Steps to reproduce the behavior
1. Setup a minikube cluster
2. Setup skaffold to build a docker image with the kubecontext set to minikube cluster
3. Note that there's no way to prevent skaffold using the minikube cluster's docker daemon
Contributor guide
Assessment
This issue has not been assessed yet.