Skip to content
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

segmentation fault starting minikube #19392

Open
sej-21 opened this issue Aug 7, 2024 · 5 comments
Open

segmentation fault starting minikube #19392

sej-21 opened this issue Aug 7, 2024 · 5 comments
Labels
co/virtualbox kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/linux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@sej-21
Copy link

sej-21 commented Aug 7, 2024

What Happened?

when i enter command minikube start i got error :segmentation fault so what i hav to do

Attach the log file

issue

Operating System

Redhat/Fedora

Driver

VirtualBox

@afbjorklund
Copy link
Collaborator

Maybe something like gdb --eval-command=run --args minikube start would help to get a proper backtrace.

You don't need to run minikube as root, and do make sure that you have enough memory in the machine.

@afbjorklund afbjorklund added os/linux co/virtualbox kind/support Categorizes issue or PR as a support question. labels Aug 7, 2024
@afbjorklund afbjorklund changed the title kubernetes segmentation fault starting minikube Aug 7, 2024
@afbjorklund afbjorklund added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. kind/bug Categorizes issue or PR as related to a bug. and removed kind/support Categorizes issue or PR as a support question. labels Aug 10, 2024
@nyufeng
Copy link

nyufeng commented Aug 19, 2024

I encountered the same issue just now. Based on my investigation, it was caused by a corrupted file due to a failed download. Simply redownloading and reinstalling should fix the problem. However, if you mistakenly executed the installation command after a failed download, be sure to delete the already installed files before trying again.

Error:
image
Success:
image

@afbjorklund
Copy link
Collaborator

afbjorklund commented Aug 19, 2024

Failed downloads would not have the same checksum, so it is unfortunate that these aren't checked by default.

Also something like --fail would have helped, maybe wcurl can fix this in the future (which curl flags to use)?

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 17, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/virtualbox kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/linux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

5 participants