You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
docker
binary name is hard-coded.. This means that if the remote host doesn't have a binary nameddocker
in the path, remote SSH support doesn't work.There are two specific use-cases this makes difficult:
docker
isn't in the path for the SSH connection, anddocker
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 baredocker
binary if set. I'll raise a PR for this change then link to it.Associated PR: #5627
Related
Would resolve #3045
The text was updated successfully, but these errors were encountered: