-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 Installer For Linux #402
Comments
Building on: #12 |
Distro packages should not be installed into a user's home directory. Packages are installed as root remember. If we're providing installers then we should follow proper file locations, e.g. /use/bin, /etc, etc |
Looks like someone has already added it to the arch user repository https://aur.archlinux.org/packages/minikube/ |
Here is a write-up detailing the steps I used in my first concept for how to a create a .deb installer for minikube: This installed the minikube binary and added it to my path on my machine (Ubuntu 14.04). I am not sure if additional dependencies should be added to the control file or what best practices would be regarding multiple binaries, directories, etc. Any suggestions on how to improve this or alternative methods would be appreciated. In another attempt, I tried to use dh-make-golang in conjunction with this guide but was not able to properly build the package getting the error: |
cc @stephenmw |
I think using |
Closing, we now have a deb and arch linux AUR package |
We are attempting to create a local installer for Minikube on all of our supported platforms and would appreciate any feedback on best practices as to how this should be designed. Right now, we are considering the following approach:
Create a bin directory in ~/.minikube:
~/minikube
--/bin/kubectl
--/bin/minikube
--/bin/drivers
Then link (via symlink, etc.) the above into the path of the user with a method that is OS specific and points to the correct minikube binary (linux os --> minikube-linux-amd64). We will create a .deb, .rpm, .dmg, and .msi to do the above.
Right now our goal is to put the minikube binary on the path of the user in a way that is extensible to multiple binaries/dependencies (kubectl, etc.), easy to maintain for all OSs, and is as fast/simple as possible.
The text was updated successfully, but these errors were encountered: