Closed byteshiva closed 5 months ago
docker.executablePath
is not a setting that exists so I'm not sure why you're expecting it to work. The setting you're looking for is docker.dockerPath
, which is intentionally allowed to contain spaces so that more complex scenarios can be used, provided the right shell quoting is in place.
{containerCommand}
and {composeCommand}
are documented here
Description: Unable to set a custom Docker executable path (
docker.executablePath
) in the settings if it already exists. This prevents customization of Docker executable paths.Steps to Reproduce:
docker.executablePath
to a custom path (e.g., "/home/xyz/.fly/bin/docker").Expected Behavior: One should be able to set a custom Docker executable path. (Especially in Exceptional Cases like Flatpak Visual Studio Code)
Proposed Solution: Permit setting
docker.executablePath
in the current settings, provided it makes logical sense in the context.Additional Note: There is no documentation(maybe i'm missing something here) on setting the
containerCommand
for Docker commands. Including this information would improve clarity.Note: -- containerCommand - I guess that it may be dynamically set at runtime from "env: withDockerEnvSettings(process.env)""."
Configuration:
or
Related: I'm trying to recreate the following scenario: https://github.com/microsoft/vscode-docker/issues/3788#issuecomment-1370345414