-
Notifications
You must be signed in to change notification settings - Fork 527
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
docker exe missing from path issue (MacOS) (again) #2894
Comments
@HannesOberreiter sorry to hear that. Did you try disabling "cloud experience" in Docker Desktop, as described by docker-archive/compose-cli#754 (comment). ? |
@karolz-ms the option was removed I think with version 3.2.x. Cheers |
I see. Hmm. Bummer. Could you do us a favor and do the following troubleshooting:
Thank you! |
@karolz-ms sure. It is included in the PATH env. |
I can confirm to have the same issue, both on macOS Big Sur on Intel chip and on macOS Big Sur on Apple chip. Maybe it is possible to disable "cloud experience" from terminal? |
@HannesOberreiter @LeaveMyYard thank you Could you also please share the exact repro steps so we can be sure we are all looking at the same codepath? |
@karolz-ms is this video sufficient or you need more? repo.mp4 |
@HannesOberreiter thank you, yes, that is very clear I have found several VS Code issues that look similar, although do not involve Docker microsoft/vscode#107169 microsoft/vscode#108003 dotnet/vscode-csharp#4037 Someone mentioned that |
@karolz-ms, thanks for your research. The mentioned |
I stumbled across this issue by accident. I can add to this discussion that this problem also exists in IntelliJ on MacOS Big Sur (Intel) with Docker Desktop since version 3.3.1. So maybe this is a Docker CLI issue and not vscode related? |
Also, docker-compose is working fine (except starting containers, because at some points it seems to run a docker command, that ends up in an error). Hope it will help. bug.report.mov |
Thank you @RobYed and @LeaveMyYard I am pretty sure this is not a VS Code Docker extension issue, and the fact that disabling "cloud experience" in Docker Desktop used to be a viable workaround makes me think it is not a VS Code core issue either. Unfortunately the workaround we added earlier this year #2619 does not seem to help I have pinged my buddies at Docker, will see what they say. We might need to consider some other workarounds in our code as proposed in #2578 ... |
The problem also exists with git Bash: |
I also faced the same issue on some other machine, where I can run the docker command on windows cmd or PowerShell, |
I am facing similar situation as well. When I try to attach to docker shell through vscode, I get the following error message
|
+1 on this issue. |
Same issue when trying to run the docker image from VSCode.
exec: "com.docker.cli": executable file not found in $PATH Terminal will be reused by tasks, press any key to close it. |
same issue here |
The workaround for me is to use the Mac Terminal instead of the integrated terminal in VS Code. macOS Big Sur version 11.4, Intel |
I am planning to add a setting ( |
I would be fine with this "workaround" as I also need to set the locations for other extensions in VSCode (e.g R and LaTeX). That means for Docker I would simply set the bin location, for example in my case Just curious if you were able to test if the workaround does work? As the error message indicates that the Cheers |
Hi Hannes, we have implemented similar workarounds for other VS Code extensions that my team owns (e.g. Dapr), so I am quite certain it will work for this extension too. |
Provides a workaround for [issue 2894](#2894)
@karolz-ms for me and another user (docker-archive/compose-cli#754 (comment)) the issue seems to be fixed with the newest VSCode update. It could have something to do with following fix (but thats only a rough guess)? microsoft/vscode#108804 Version: 1.57.0
Commit: b4c1bd0a9b03c749ea011b06c6d2676c8091a70c
Date: 2021-06-09T17:22:31.215Z (4 days ago)
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin x64 20.3.0 Cheers |
@HannesOberreiter possibly. Thanks for letting us know. We will keep the "Docker CLI path" setting just in case. |
Workaround has shipped in 1.14 release |
@karolz-ms thanks a lot for your work! |
Description:
Docker executable cannot be found. It throws following error:
This problem was previously reported and fixed. It worked for me without any problems for a few weeks. Now it is broken again (at least for me).
Previous Discussion:
#2578
Discussion on Docker:
docker-archive/compose-cli#754
Discussion of possible fixed on Stackoverflow:
https://stackoverflow.com/questions/64120020/exec-com-docker-cli-executable-file-not-found-in-path
What I tried so far to fix it again:
Versions:
vscode-Docker: 1.12.1
Docker Engie: 20.10.5
Docker Desktop: 3.3.1
macOS Big Sur, 11.2.3 (Intel)
My results from PATH Checking:
Cheers
Hannes
The text was updated successfully, but these errors were encountered: