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

getting error while running minikube start #19983

Open
Gopikrishna-marri opened this issue Nov 21, 2024 · 4 comments
Open

getting error while running minikube start #19983

Gopikrishna-marri opened this issue Nov 21, 2024 · 4 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@Gopikrishna-marri
Copy link

What Happened?

S C:\Users\Dell> minikube start

  • minikube v1.34.0 on Microsoft Windows 10 Pro 10.0.19045.5131 Build 19045.5131
  • Using the virtualbox driver based on existing profile
  • Starting "minikube" primary control-plane node in "minikube" cluster
  • Updating the running virtualbox "minikube" VM ...
    ! StartHost failed, but will try again: provision: Error getting config for native Go SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.
  • Updating the running virtualbox "minikube" VM ...
  • Failed to start virtualbox VM. Running "minikube delete" may fix it: provision: Error getting config for native Go SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.

X Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: provision: Error getting config for native Go SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
https://github.com/kubernetes/minikube/issues/new/choose
│ │
│ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue.

Attach the log file

S C:\Users\Dell> minikube start

  • minikube v1.34.0 on Microsoft Windows 10 Pro 10.0.19045.5131 Build 19045.5131
  • Using the virtualbox driver based on existing profile
  • Starting "minikube" primary control-plane node in "minikube" cluster
  • Updating the running virtualbox "minikube" VM ...
    ! StartHost failed, but will try again: provision: Error getting config for native Go SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.
  • Updating the running virtualbox "minikube" VM ...
  • Failed to start virtualbox VM. Running "minikube delete" may fix it: provision: Error getting config for native Go SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.

X Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: provision: Error getting config for native Go SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
https://github.com/kubernetes/minikube/issues/new/choose
│ │
│ * Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue.

Operating System

Windows

Driver

VirtualBox

@T-Lakshmi
Copy link

This issue is duplicate of #11855.

/triage duplicate

@k8s-ci-robot k8s-ci-robot added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Nov 22, 2024
@T-Lakshmi
Copy link

@Gopikrishna-marri,
The issue you encountered because you don't have access to your id_rsa file.

SSH: open C:\Users\Dell.minikube\machines\minikube\id_rsa: Access is denied.

Check the suggestion mentioned in #11855 comment to resolve the issue.
Let us know if you are still facing issue after following this.

@T-Lakshmi
Copy link

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Nov 22, 2024
@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 Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

4 participants