Skip to content

Minikube: Cleanup everything to start new machine #12749

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Mar 8, 2019
Merged

Minikube: Cleanup everything to start new machine #12749

merged 2 commits into from
Mar 8, 2019

Conversation

@iamneha
Copy link
Contributor

@iamneha iamneha commented Feb 21, 2019

Fixes issue: #12588

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 21, 2019
@netlify
Copy link

netlify bot commented Feb 21, 2019 •
edited
Loading

Deploy preview for kubernetes-io-master-staging ready!

Built with commit e612959

https://deploy-preview-12749--kubernetes-io-master-staging.netlify.com

daminisatya
daminisatya reviewed Feb 21, 2019
View reviewed changes
content/en/docs/tasks/tools/install-minikube.md Outdated
{{% /capture %}}

## Cleanup everything to start fresh
If you have installed minikube before and when running `minikube start` is throwing error `machine does not exist` then simply wipe existing configuration files.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not just machine does not exist error, I faced another issue where removing the config file helped.

  • Minikube start used to get stuck at starting the VM, and when checked the logs, I would only see a timeout error in a never-ending loop for a particular API call (Not sure which one particularly)

Maybe can we frame this a little generic?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iamneha This needs better wording. Consider:

Starting fresh after a previous installation

If you have previously installed minikube, and run:

minikube start

If this command returns an error:

machine does not exist

You need to wipe the configuration files:

@iamneha
Copy link
Contributor Author

iamneha commented Feb 21, 2019 •
edited
Loading

@daminisatya
Maybe you saw this error

$ minikube start                                    
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0221 14:59:41.221423   25128 start.go:168] Error starting host: Temporary Error: Error configuring auth on host: OS type not recognized.

@daminisatya What the generic update you suggest?

@daminisatya
Copy link
Contributor

daminisatya commented Feb 21, 2019 •
edited
Loading

No @iamneha , not this. I will try to reproduce the error and give you the logs if possible.
And I will get back to you wiith a generic sentence.

@iamneha iamneha changed the title Minikube: Cleanup everything to start new machine [WIP] Minikube: Cleanup everything to start new machine Feb 22, 2019
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 22, 2019
zacharysarah
zacharysarah suggested changes Mar 7, 2019
View reviewed changes
Copy link
Contributor

@zacharysarah zacharysarah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iamneha Thanks for this update. This PR needs better wording before it can merge.

content/en/docs/tasks/tools/install-minikube.md Outdated
{{% /capture %}}

## Cleanup everything to start fresh
If you have installed minikube before and when running `minikube start` is throwing error `machine does not exist` then simply wipe existing configuration files.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iamneha This needs better wording. Consider:

Starting fresh after a previous installation

If you have previously installed minikube, and run:

minikube start

If this command returns an error:

machine does not exist

You need to wipe the configuration files:

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 8, 2019
@iamneha
Copy link
Contributor Author

iamneha commented Mar 8, 2019

Thanks @zacharysarah
I have updated this PR. Please check

@zacharysarah
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 8, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zacharysarah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2019
@iamneha iamneha changed the title [WIP] Minikube: Cleanup everything to start new machine Minikube: Cleanup everything to start new machine Mar 8, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 8, 2019
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 8, 2019
@iamneha iamneha mentioned this pull request Mar 8, 2019
Closed
6 tasks
@zacharysarah
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 8, 2019
@k8s-ci-robot k8s-ci-robot merged commit 92e602c into kubernetes:master Mar 8, 2019
krmayankk pushed a commit to krmayankk/kubernetes.github.io that referenced this pull request Mar 11, 2019
@iamneha
Minikube: Cleanup everything to start new machine (kubernetes#12749)
c108373 
* Minikube: Cleanup everything to start new machine

* Quick fixes
yagonobre pushed a commit to yagonobre/website that referenced this pull request Mar 14, 2019
@iamneha @yagonobre
Minikube: Cleanup everything to start new machine (kubernetes#12749)
12a3969 
* Minikube: Cleanup everything to start new machine

* Quick fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@stewart-yu stewart-yu Awaiting requested review from stewart-yu

@zhangxiaoyu-zidif zhangxiaoyu-zidif Awaiting requested review from zhangxiaoyu-zidif

2 more reviewers

@daminisatya daminisatya daminisatya left review comments

@zacharysarah zacharysarah zacharysarah requested changes

Reviewers whose approvals may not affect merge requirements

Assignees

@zacharysarah zacharysarah

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@iamneha @daminisatya @zacharysarah @k8s-ci-robot