0

I am trying to execute sudo docker -H 192.168.100.11 ps from machine A (on remote host), and it does not respond in any way (Ctrl+C closes call).

Same time, sudo docker -H 192.168.100.11 version from A runs smoothly.

Running command sudo docker -H 192.168.100.11 ps from another machine (within another network), let's say B, is OK.

I can connect to dockerd port 2375 from both machines A and B, and /_ping endpoint is fine

Telnet example:

$ telnet 192.168.100.11 2375
GET /_ping HTTP/1.1
Host: host

HTTP/1.1 200 OK
Api-Version: 1.41
Cache-Control: no-cache, no-store, must-revalidate
Docker-Experimental: false
Ostype: linux
Pragma: no-cache
Server: Docker/20.10.11 (linux)
Date: Thu, 15 Dec 2022 06:47:27 GMT
Content-Length: 2
Content-Type: text/plain; charset=utf-8

OK

What type of issue it could be? where should I look?

Machines A and B are in different subnets (A in 192.168.1.0/24, B in 192.168.100.0/24), so I am trying to access subnet B from A. But it is reachable (as we could see on 3rd screenshot)

Norritt
  • 1
  • 2
  • after moving dockerd in debug mode (`-D`) and adjusting loglevel to debug (`-l debug`) I found that issue was caused due to connectivity – Norritt Dec 19 '22 at 21:20

0 Answers0