You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to resolve the current Docker CLI context "default": context "default": context not found XXXXX : The system cannot find the path specified.
#18776
Open
krolle08 opened this issue
Apr 30, 2024
· 2 comments
I've embarked on my journey to understand Kubernetes, so please bear with me if I ask some obvious questions.
I've successfully set up Minikube locally, and it runs smoothly. However, after installing Docker (although I haven't yet utilized it), I encounter an error message. Despite this, Minikube still starts and stops without any further issues. It seems like it tries to execute a meta.json file inside the .docker\context\meta folder.
I´ve tried to activate the Linux subsystem feature on windows to run the app WSL to see if any issues could be found in systemctl, but the windows version of WSL does not support systemctl.
A solution is to simply uninstall docker and then the error message disappears, but I would like to understand the problem and how to solve it.
If any help, this is the content of the meta.json file:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Windows\system32> minikube start W0430 09:05:20.921653 15388 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\XXXX\XXXX.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified. * minikube v1.33.0 on Microsoft Windows 11 Pro 10.0.22631.2861 Build 22631.2861 * Using the hyperv driver based on existing profile
Starting "minikube" primary control-plane node in "minikube" cluster
Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
PS C:\Windows\system32> docker version
error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.45/version": open //./pipe/docker_engine: The system cannot find the file specified.
Client:
Cloud integration: v1.0.35+desktop.13
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:18:56 2024
OS/Arch: windows/amd64 Context: default PS C:\Windows\system32> docker version Client: Cloud integration: v1.0.35+desktop.13 Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:18:56 2024 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.29.0 (145265) Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:18:01 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
PS C:\Windows\system32> minikube stop
W0430 09:07:00.497089 30220 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\XXXX\XXXX.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
Stopping node "minikube" ...
Powering off "minikube" via SSH ...
1 node stopped.
PS C:\Windows\system32> systemctl
systemctl : The term 'systemctl' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
PS C:\Windows\system32> systemd
systemd : The term 'systemd' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
PS C:\Windows\system32> minikube start
W0430 09:25:38.235022 28004 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\XXXX\XXXX.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
minikube v1.33.0 on Microsoft Windows 11 Pro 10.0.22631.2861 Build 22631.2861
Using the hyperv driver based on existing profile
Starting "minikube" primary control-plane node in "minikube" cluster
Maybe you run it by desktop-linux, I had the same issue and it can be fixed by creating one folder in C:\Users\${USER}\.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f and copy the meta.json file from another folder (e.g. fe9c6bd7a66301f49ca9b6a70b217107cd1284598bfc254700c989b916da791e) into it.
What Happened?
I've embarked on my journey to understand Kubernetes, so please bear with me if I ask some obvious questions.
I've successfully set up Minikube locally, and it runs smoothly. However, after installing Docker (although I haven't yet utilized it), I encounter an error message. Despite this, Minikube still starts and stops without any further issues. It seems like it tries to execute a meta.json file inside the .docker\context\meta folder.
I´ve tried to activate the Linux subsystem feature on windows to run the app WSL to see if any issues could be found in systemctl, but the windows version of WSL does not support systemctl.
A solution is to simply uninstall docker and then the error message disappears, but I would like to understand the problem and how to solve it.
If any help, this is the content of the meta.json file:
{
"Name": "desktop-linux",
"Metadata": {
"Description": "Docker Desktop",
"otel": {
"OTEL_EXPORTER_OTLP_ENDPOINT": "unix://C:\XXXX\XXXX\AppData\Local\Docker\run\userAnalyticsOtlpHttp.sock"
}
},
"Endpoints": {
"docker": {
"Host": "npipe:////./pipe/dockerDesktopLinuxEngine",
"SkipTLSVerify": false
}
}
}
Attach the log file
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Windows\system32> minikube start W0430 09:05:20.921653 15388 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\XXXX\XXXX.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified. * minikube v1.33.0 on Microsoft Windows 11 Pro 10.0.22631.2861 Build 22631.2861 * Using the hyperv driver based on existing profile
PS C:\Windows\system32> docker version
error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.45/version": open //./pipe/docker_engine: The system cannot find the file specified.
Client:
Cloud integration: v1.0.35+desktop.13
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:18:56 2024
OS/Arch: windows/amd64 Context: default PS C:\Windows\system32> docker version Client: Cloud integration: v1.0.35+desktop.13 Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:18:56 2024 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.29.0 (145265) Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:18:01 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
PS C:\Windows\system32> minikube stop
W0430 09:07:00.497089 30220 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\XXXX\XXXX.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
PS C:\Windows\system32> systemctl
systemctl : The term 'systemctl' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
PS C:\Windows\system32> systemd
systemd : The term 'systemd' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
PS C:\Windows\system32> minikube start
W0430 09:25:38.235022 28004 main.go:291] Unable to resolve the current Docker CLI context "default": context "default": context not found: open C:\XXXX\XXXX.docker\contexts\meta\37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f\meta.json: The system cannot find the path specified.
PS C:\Windows\system32> minikube stop
PS C:\Windows\system32>
Operating System
Windows
Driver
Hyper-V
The text was updated successfully, but these errors were encountered: