[ci] fix networking flakiness on s390x, ppc64le, GitHub actions #41561
Description
Networking seems to be flaky on these machines, which could either be a regression in our code, or an issue with those machines;
e.g. https://ci-next.docker.com/public/blue/organizations/jenkins/moby/detail/PR-41560/1/tests
If things are failing, it's always these 5 tests that fail
=== RUN TestNetworkNat
--- FAIL: TestNetworkNat (0.93s)
nat_test.go:34: assertion failed: error is not nil: dial tcp 172.17.0.2:8080: connect: connection refused
=== RUN TestNetworkLocalhostTCPNat
--- FAIL: TestNetworkLocalhostTCPNat (0.83s)
nat_test.go:56: assertion failed: hi yall (msg string) != (string)
=== RUN TestNetworkLoopbackNat
--- FAIL: TestNetworkLoopbackNat (0.89s)
nat_test.go:73: assertion failed: error is not nil: Error response from daemon: cannot join network of a non running container: b3f5f9e2779db128024c71b846f821d2d18d252d2546c1e981e973c5abdded92
=== RUN TestRenameAnonymousContainer
--- FAIL: TestRenameAnonymousContainer (4.74s)
rename_test.go:168: assertion failed: 0 (int) != 1 (inspect.State.ExitCode int): container b6bce65915581694f27546bf46d4f70bd71497f7308642b22a24f20ab6ed9b95 exited with the wrong exitcode:
== RUN TestHostnameDnsResolution
--- FAIL: TestHostnameDnsResolution (1.74s)
run_linux_test.go:134: assertion failed:
--- ←
+++ →
@@ -1 +1,2 @@
+ping: bad address 'foobar'
run_linux_test.go:135: assertion failed: 0 (int) != 1 (res.ExitCode int)