docker exe missing from path issue (MacOS) (again)

[HannesOberreiter]

Description:
Docker executable cannot be found. It throws following error:

exec: "com.docker.cli": executable file not found in $PATH

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:

• reinstall docker and cli
• reinstall vscode-docker
• (rebooting)

---

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

[karolz-ms]

@HannesOberreiter sorry to hear that. Did you try disabling "cloud experience" in Docker Desktop, as described by docker-archive/compose-cli#754 (comment). ?

[HannesOberreiter]

@karolz-ms the option was removed I think with version 3.2.x.

Cheers
Hannes

[karolz-ms]

I see. Hmm. Bummer.

Could you do us a favor and do the following troubleshooting:

1. Try to reproduce the issue. Do not close the VS Code terminal that reports Docker exe not found error.
2. Find the PID of the terminal process that reported the error (it will be one of the VS Code processes that has --type=ptyHost argument applied)
3. Do ps eww <PID> on that process and report if the PATH environment variable contains /usr/local/bin.

Thank you!

[HannesOberreiter]

@karolz-ms sure.

It is included in the PATH env.

[LeaveMyYard]

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?

[karolz-ms]

@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?

[HannesOberreiter]

@karolz-ms is this video sufficient or you need more?

repo.mp4

[karolz-ms]

@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 Developer: reload window gesture seems to fix at least some extension. Can you try and report whether that is a good workaround?

[HannesOberreiter]

@karolz-ms, thanks for your research. The mentioned Developer: reload window did not help. Opening VSCode from Application and not via Terminal did also not help.

[RobYed]

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?

[LeaveMyYard]

@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?

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

[karolz-ms]

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 ...

[alanmazuco]

The problem also exists with git Bash:
"com.docker.cli": executable file not found in %PATH%
On Windows Power Shell it works fine.