The error below can be caused by a gateway that is unpingable:

docker swarm join --token SWMTKN-1-1kogg8da68gtb1j7ezaddowyy9s0an5s9tue758o20k18liskw-5h3f61hrrmv3u6agshvbtcklf 172.16.1.80:2377
Error response from daemon: manager stopped: can't initialize raft node: rpc error: code = Unknown desc = could not connect to prospective new cluster member using its advertised address: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Nov 28 02:01:52 dockertest01 dockerd[14612]: time="2023-11-28T02:01:52.189193519-05:00" level=warning msg="Failed to dial 172.16.1.1:2377: grpc: the connection is closing; please retry." module=grpc

The error below doesn't make sense at first, you join a certain IP but the error comes back as trying to connect to a different IP. 

This can be caused my forwarding and / or proxies which should be disabled to fix the problem.

Even with pingable gateway it now wants to somehow connect on port 2377 through the gateway instead of the .80 manager node IP?

 docker swarm join --token SWMTKN-1-1kogg8da68gtb1j7ezaddowyy9s0an5s9tue758o20k18liskw-5h3f61hrrmv3u6agshvbtcklf 172.16.1.80:2377
Error response from daemon: manager stopped: can't initialize raft node: rpc error: code = Unknown desc = could not connect to prospective new cluster member using its advertised address: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 172.16.1.1:2377: connect: connection refused"


docker, swarm, issuesthe, gateway, unpingable, token, swmtkn, kogg, gtb, ezaddowyy, tue, liskw, hrrmv, agshvbtcklf, daemon, initialize, raft, node, rpc, desc, prospective, cluster, advertised, deadlineexceeded, context, deadline, exceeded, nov, dockertest, dockerd, quot, msg, grpc, retry, module, doesn, ip, forwarding, proxies, disabled, pingable, unavailable, subconns, transientfailure, dialing, tcp,

Latest Articles