-
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
mac/hyperkit: /usr/bin/kubeadm alpha phase addon kube-dns .: Process exited with status 1 #3264
Comments
https://github.com/kvokka/run-minikube may help tested with minikube 0.30 && macOS 10.14 |
Everything in that process is supposed to work (assuming the use of |
I currently use VMWare, but have tried Hyperkit too. A fresh install There seems to be a heap of related issues since v0.26.0. e.g. #2886 @afbjorklund how do we get the |
Had the same issue on Windows with HyperV after upgrade to v0.30.0...
|
Reinstalling everything (that is, the hyperkit executable, and minikube)
didn't fix my issue on Mac OS.
Yes, also curious about how I can get the `kubeadm` log.
…On Tue, Oct 23, 2018 at 2:56 AM Allan Chau ***@***.***> wrote:
I currently use VMWare, but have tried Hyperkit too.
A fresh install rm -rf ~/.minikube ~/.kube and minikube start
--vm-driver=hyperkit minikube start --vm-driver=vmwarefusion has been
broken since v0.26.0.
Running macOS 10.13 and now 10.14.
There seems to be a heap of related issues since v0.26.0. e.g. #2886
<#2886>
@afbjorklund <https://github.com/afbjorklund> how do we get the kubeadm
log? Is there anything else that would help?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3264 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVhGyRflh7qrqCuDTsVOCse_PBA367Eks5unmk2gaJpZM4XwBKH>
.
|
I'm not sure what the "official" way is... I normally just run the same command over ping @tstromberg |
I am also facing this issue, as a workaround I am using the |
@cbrewster Can you please say, why exactly that version (and that version)? Did you tried 0.26? or any other? |
I tried 0.26 and it didn't work as mentioned in #3264 (comment) (it hangs on Starting cluster components... just like v0.30.0) I tried running with
|
Also having this exact same issue OS X 10.14.1 Hangs at
|
minikube v0.33 now shows why kubeadm failed, so if you run into this again - please open a new bug. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
This is a bug report.
Please provide the following details:
Environment:
Minikube version: 0.30.0
What happened:
I'm trying to run qinikube on my machine, and here is the output:
What you expected to happen:
I expected the machine to be generated, and I got an error instead.
How to reproduce it (as minimally and precisely as possible):
Run
minikube start --vm-driver=hyperkit
on Mac OSAnything else do we need to know:
This issue exists for a while now, and previously I was getting around it by using the
--bootstrapper=localkube
option. However, ow that--bootstrapper
is removed, I have no idea how to fix this.The text was updated successfully, but these errors were encountered: