Open jandubois opened 1 month ago
Check if #7146 might be the reason for this failure as well.
First test would be to check if the failure is limited to containerd
and does not happen with moby
.
See also #7147 for a possible workaround (manually restart the guestagent after k3s
was restarted) until #7146 is fixed.
We expect a
curl
command to a closed port to returncurl: (7) Failed to connect
.Instead on Windows 11 I receive
curl: (56) Recv failure: Connection was reset
for port 80 andcurl: (35) Recv failure: Connection was aborted
for port 443.The follow log is for the
localhost
test, but the same result is returned forhost-ip
. This result has been reproducible over multiple attempts by runningRelevant log section:
I believe the same test ran successfully for @Nino-K on Windows 10, but I'm not sure if he used the same k3s version etc.