W0808 15:36:19.352245 24080 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\LENOVO\.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.

[vaidyaes]

What Happened?

W0808 15:36:19.352245 24080 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\LENOVO.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
! Executing "docker container inspect minikube --format={{.State.Status}}" took an unusually long time: 19.4654767s

• Restarting the docker service may improve performance.

X Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": context deadline exceeded
*
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * 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. │
│ * Please also attach the following file to the GitHub issue: │
│ * - C:\Users\LENOVO\AppData\Local\Temp\minikube_logs_d3038d48338bd5ba63abf408f868200ab1a9066a_0.log │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Attach the log file

C:\Windows\System32>minikube logs --file=logs.txt
W0808 15:36:19.352245 24080 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\Users\LENOVO.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
! Executing "docker container inspect minikube --format={{.State.Status}}" took an unusually long time: 19.4654767s

• Restarting the docker service may improve performance.

X Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": context deadline exceeded
*
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * 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. │
│ * Please also attach the following file to the GitHub issue: │
│ * - C:\Users\LENOVO\AppData\Local\Temp\minikube_logs_d3038d48338bd5ba63abf408f868200ab1a9066a_0.log │
│

Operating System

Windows

Driver

Docker

[anmolsekhon590]

I have the same issue on my Windows PC

[Bahri-Haythem]

Same here on Windows. I tried this solution , it works but once I restart my PC the error reappear

[k8s-triage-robot]

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-triage-robot]

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-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.