When using remote Podman, k3d complains that the docker CLI is not available on the remote host.
What did you do
- followed Using remote Podman
k3d cluster create
What did you expect to happen
The cluster gets up properly
Screenshots or terminal output
... command [ssh -o ConnectTimeout=30 -l {user_name} -p {port} -- {host} docker system dial-stdio] has exited with exit status 127, make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=bash: line 1: docker: command not found
Which OS & Architecture
Fedora Linux 42 (Cloud Edition)
Which version of k3d
5.8.3
Which version of docker
podman version 5.5.0
Possible solution
Use the value of DOCKER_SOCK to determine the correct CLI on the remote host.
When using remote Podman,
k3dcomplains that thedockerCLI is not available on the remote host.What did you do
k3d cluster createWhat did you expect to happen
The cluster gets up properly
Screenshots or terminal output
... command [ssh -o ConnectTimeout=30 -l {user_name} -p {port} -- {host} docker system dial-stdio] has exited with exit status 127, make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=bash: line 1: docker: command not foundWhich OS & Architecture
Fedora Linux 42 (Cloud Edition)
Which version of
k3d5.8.3
Which version of docker
podman version 5.5.0
Possible solution
Use the value of
DOCKER_SOCKto determine the correct CLI on the remote host.