Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente...
by JustinGarrison on Wednesday July 06, 2016 @12:52PM
(#12044317)
Why does minikube use a VM layer on Linux? Is it just for flexibility and not using the local docker daemon?
[ Parent
| on HN ]
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente...
by dlor on Wednesday July 06, 2016 @12:58PM
(#12044374)
We mainly use the VM to provide a well-known and tested environment for Kubernetes to run in. Running inside a Docker container on Linux would have similar benefits, but there are still a few bugs with running some of the Kubernetes components inside containers.
We'll probably add a "native" option for Linux at some point. See this issue: https://github.com/kubernetes/minikube/issues/261 for a little more conversation.
Disclosure: I work at Google, on Minikube.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente...
by NetStrikeForce on Wednesday July 06, 2016 @01:02PM
(#12044406)
This is very cool, finally I don't need a datacentre to test some things :)
thanks!
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente...
by moosingin3space on Wednesday July 06, 2016 @01:33PM
(#12044612)
I don't know if this is why, but when I work with Docker on Linux, I prefer to use docker-machine's VM layer because that way, I don't need to run docker commands as root.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente...
by JustinGarrison on Wednesday July 06, 2016 @01:42PM
(#12044667)
My only complaint with the VM layer is it's harder to have faster iterations with local development. I know this isn't the documented way to develop with kubernetes but I often use containers with -v $PWD:/app to test things interactively
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente...
by moosingin3space on Wednesday July 06, 2016 @02:43PM
(#12045026)
Ahh, now that makes sense. I don't usually develop inside a container, so that's why I haven't had this issue before.