Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube should (build and) use the latest localkube binary #53

Closed
luxas opened this issue May 9, 2016 · 2 comments
Closed

Minikube should (build and) use the latest localkube binary #53

luxas opened this issue May 9, 2016 · 2 comments

Comments

@luxas
Copy link
Member

luxas commented May 9, 2016

No description provided.

@dlorenc
Copy link
Contributor

dlorenc commented May 10, 2016

Here's what I'm thinking here:

Building minikube from scratch should do the following:

  • build localkube for linux/amd64 with cgo enabled
  • run go-bindata to add the localkube binary to the minikube source
  • build minikube for the target platform

Then when you start the cluster, minikube can transfer the file to the VM from memory.

This has a few problems though:

  • building localkube is slow
  • cross compiling with cgo is hard

So we could have a second, "quick" compile mode for minikube that uses a separate build of localkube instead of building one from head.

Then whenever someone changes localkube, we'll update the separate build of localkube as well.

Thoughts?

@dlorenc
Copy link
Contributor

dlorenc commented May 13, 2016

Closed with #66

@dlorenc dlorenc closed this as completed May 13, 2016
jimmidyson added a commit to jimmidyson/minikube that referenced this issue Sep 2, 2016
Use a static UUID for the xhyve driver so that if you re-create, then…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants