Enable TCP Path MTU Discovery when an ICMP black hole is detected #9537
+7
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partial fix for #9528 - the longer-term fix will come from #9530
This lets
docker pull
work when the network MTU is misconfigured. There are no apparent downsides to this approach, as best as I can tell. Here's the documentation from https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txtNOTE That
tcp_base_mss
defaults to 1024. I believe that 1 is the best default going forward.I can confirm that this allows
minikube ssh "docker pull golang:1.15"
to work properly on Cloud Shell.Old behavior
New behavior