Support resolving Docker from $PATH in extension command

[nquinquenel]

Check for existing issues

• Completed

Misc notes

Description:
Hello, I am developing an MCP server that runs via Docker. While creating a Zed extension for this MCP, I noticed that specifying docker in the command does not work, since it is not resolved from the system’s $PATH.

Using the full path (e.g. /usr/bin/docker) works as expected, but this is not portable and requires extra configuration across environments.

Currently, there is support for resolving executables like node from $PATH. Could we have similar support for docker?

What I’ve tried:
Using which crate to resolve the path → not compatible due to WASM compilation.

Running OS-dependent commands (which, where) → not usable for the same reason.

Feature request:
Please add support for resolving docker from $PATH when launching the extension, so developers don’t need to hardcode full paths.
If there is a workaround, I'd happily hear about it. Thanks!