There are two specific use-cases this makes difficult:
Systems where docker isn't in the path for the SSH connection, and
Systems where the docker binary has another name.
If this hard-coded default could be overridden, these use-cases could be supported.
Proposal
Introduce the DOCKER_SSH_REMOTE_BINARY environment variable, which will be used in place of the bare docker binary if set. I'll raise a PR for this change then link to it.
Description
Currently, when connecting to a remote SSH host, the
dockerbinary name is hard-coded.. This means that if the remote host doesn't have a binary nameddockerin the path, remote SSH support doesn't work.There are two specific use-cases this makes difficult:
dockerisn't in the path for the SSH connection, anddockerbinary has another name.If this hard-coded default could be overridden, these use-cases could be supported.
Proposal
Introduce the
DOCKER_SSH_REMOTE_BINARYenvironment variable, which will be used in place of the baredockerbinary if set. I'll raise a PR for this change then link to it.Associated PR: https://github.com/docker/cli/pull/5627
Related
Would resolve https://github.com/docker/cli/issues/3045