3 ms·
Is your issue with building containers and getting them into the minikube VM? If so, you can use "eval $(minikube docker-env)" to make your shell's docker comm
by figpope 8y ago
Is your issue with building containers and getting them into the minikube VM?
If so, you can use "eval $(minikube docker-env)" to make your shell's docker commands talk to the docker daemon in the VM.
- linkmotif 8y agoRunning a VM is a total drag. I only have 16GB RAM. Then even if I run a VM, the docker registry is not the same as my production docker registry (GCR). I guess I can account for this with a variable in my helm templates, but then it’s just more complexity. Would you recommend minikube even with 16GB RAM? How much do you allot to the VM?
- gkop 8y agoI'm a long-time minikube fan, I like the isolation (totally worth whatever minor VM memory overhead), reliability, ease-of-use; it feels like an appliance in a good way, which is something I traditionally associate with VMs. minikube contributed strongly to me personally getting excited about k8s in 2016. The local docker registry is an asset because it gives me flexible when offline.
- linkmotif 8y agoThank you for your report! I will look into this.