C:\YADAMU>docker context ls
NAME TYPE DESCRIPTION DOCKER ENDPOINT
KUBERNETES ENDPOINT ORCHESTRATOR
default moby Current DOCKER_HOST based configuration npipe:////./pipe/docker_engine
desktop-linux moby Docker Desktop npipe:////./pipe/dockerDesktopLinuxEngine
yadamu-db1 * moby ssh://yadamu@yadamu-db1
C:\YADAMU>docker exec -it ORA1903-01 mkdir -p /tmp/foo
C:\YADAMU>docker exec -it ORA1903-01 mkdir -p /tmp/foo
command [ssh -o ConnectTimeout=30 -l yadamu -- yadamu-db1 docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh: Could not resolve hostname yadamu-db1: No such host is known.
C:\YADAMU>
C:\YADAMU>docker exec -it ORA1903-01 mkdir -p /tmp/foo
C:\YADAMU>docker exec -it ORA1903-01 mkdir -p /tmp/foo
command [ssh -o ConnectTimeout=30 -l yadamu -- yadamu-db1 docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh: Could not resolve hostname yadamu-db1: No such host is known.
C:\YADAMU>
I can ssh without issues
C:\YADAMU>ssh yadamu@yadamu-db1
Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 5.17.0-1019-oem x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
System information as of Sun Oct 1 07:29:34 PM UTC 2023
System load: 0.3447265625
Usage of /: 11.8% of 1.79TB
Memory usage: 11%
Swap usage: 12%
Temperature: 75.0 C
Processes: 985
Users logged in: 0
IPv4 address for br-57adaa1c0b26: 172.19.0.1
IPv4 address for docker0: 172.17.0.1
IPv4 address for enp91s0: 192.168.1.230
* Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
just raised the bar for easy, resilient and secure K8s cluster deployment.
https://ubuntu.com/engage/secure-kubernetes-at-the-edge
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
16 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm
Docker commands are being run on Windows 11
Server Version is
yadamu@yadamu-db1:~$ docker -v
Docker version 24.0.6, build ed223bc
yadamu@yadamu-db1:~$
Client Version is
C:\YADAMU>docker -v
Docker version 24.0.6, build ed223bc
C:\YADAMU>
I am seeing this problem from two seperate windows clients trying to work with 2 seperate linux servers. The Server Side SSH logs show an open without a corresponding close when the error occurs. When the error does not occur the ssh log shows each open opeation has a corresponding close.