-
Notifications
You must be signed in to change notification settings - Fork 72
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
alternative boot2docker ISO image (minikube-iso) support #135
Comments
@s-urbaniak Hmm... ok. (If I remember right, this error also occurs fuchsia-mirror/magenta's forked qemu. I will investigate.) |
@s-urbaniak Ah, remembered. fuchsia-mirror/magenta also uses buildroot kernel. |
@s-urbaniak Also, If you have time, could you try launch that ISO uses original xhyve or hyperkit? If both of failed, docker-machine-driver-xhyve also not supported. Needs C languages level hack(or workaround?). Edit: If you not familiar with xhyve or hyperkit, I will test it. |
@zchee not too familiar to be honest, since I am actually a Linux user only ;-) If you have spare cycles to give it a shot with xhyve, that would be great :-) |
@s-urbaniak OK, np! Anyway, I will investigate later :) |
@zchee this is for minikube :-) |
@s-urbaniak ok :) |
@s-urbaniak Sorry, reference for me. What kubenetes team's goal? |
@zchee Kubernetes as of 1.3 also supports rkt as an additional container runtime next to Docker. Furthermore there is a container runtime interface specification out there [1] which abstracts container runtime support inside Kubernetes even more. |
@s-urbaniak Ah, sorry. My question is bad... :( In other words, What I should be run any iso? So, What do you want to run the iso file instead of boot2docker.iso? I cannot use English well, so please forgive me if I say something rude. |
@zchee no, problem, I appreciate the help :-) To try out the ISO, simply execute:
Note: you must have minikube 0.10.0 (https://github.com/kubernetes/minikube/releases/tag/v0.10.0). |
@s-urbaniak OK thanks. will try it. BTW, I've also joined kubenetes Slack channel. Could you help in there? |
@zchee sure thing! |
Current state: https://github.com/coreos/minikube-iso/issues/17 |
So with the two PRs I just sent: #144 and #143 I got this to boot with the new ISO! $ minikube start --iso-url=http://storage.googleapis.com/minikube/iso/buildroot/minikube-v0.0.6.iso --vm-driver=xhyve --show-libmachine-logs --v=100 Unfortunately this doesn't work with the old ISO though. I took a look and the xhyve commands run seem the same, but I might be missing something. @zchee is there anything else missing in this branch to work with both ISOs? |
Nevermind, I'm not sure what happened but my PR #144 works with both ISOs :) |
xhyve driver already support minikube iso. |
#147 has been merged, and I was released v0.3.0. |
in boot2doecker when i start minikube , they ask minikube login and minikube password. what are the default values ? |
Hi,
I am building an alternative boot2docker image called minikube-iso https://github.com/coreos/minikube-iso for the https://github.com/kubernetes/minikube project which include systemd, as well as the rkt container runtime. The ISO is built using http://buildroot.org.
When starting using the following command:
Especially the
vm exit[0]
apparently indicates something, but I am not able to reason about the output. I am sorry, that this lies outside of the "regular" boot2docker ISO, but any help/hint would be helpful. Am i missing some kernel module maybe?Here is the kernel configuration: https://github.com/s-urbaniak/minikube-iso/blob/xhyve-support/board/coreos/minikube/linux-4.7_defconfig
PS: Creating a minikube instance using
minikube start --vm-driver=xhyve
works.Thanks for any hints!
The text was updated successfully, but these errors were encountered: