-
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
Can't start cluster when using profile option #2913
Comments
It should be noted that I am able to start a cluster with the profile option when I use minikube built from master. |
|
I guess this relates to #2717 for which the fix has now been merged into master. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Dupe of #2574 |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug
Environment:
What happened:
Starting a cluster with
-p
fails.What you expected to happen:
A cluster is created using the specified profile.
How to reproduce it (as minimally and precisely as possible):
minikube start -p foo
Output of
minikube logs
(if applicable):^^ From stdout and
from minikube logs
Anything else do we need to know:
The text was updated successfully, but these errors were encountered: