Open danog opened 1 month ago
For future reference, the "fix" was to manually edit the docker.json config file through the Docker desktop settings => Docker engine, adding an "mtu": yourMTU,
entry, where your MTU is the correct MTU of your connection, if not known beforehand, can be determined by running the following command:
ping example.com -D -s $((1500 - 28))
Decrease 1500 gradually (1 by 1) until ping succeeds, then set the MTU to that value both in Docker and in the Mac OS system settings.
Unfortunately, both Mac OS and docker desktop completely ignore the MTU advertised by the router using DHCP and RAs.
However, this is also a Docker Desktop bug, because it should automatically configure the MTU based on the MTU of the current connection, configured in the settings.
Contributing guidelines
I've found a bug and checked that ...
Description
Copy of https://github.com/docker/buildx/issues/350, since the root cause wasn't fixed yet.
Getting continuous TLS timeouts when doing multiarch builds on mac OS 15.0.1, i.e:
To reproduce, simply limit the MTU of your connection (i.e. at the router) to a value smaller than 1500 (in my case 1492, actually very common on PPPoE connections that do not support jumbo frames, or on VPNs).
Expected behaviour
No TLS timeouts
Actual behaviour
TLS timeouts
Buildx version
github.com/docker/buildx v0.16.2-desktop.1 081c21b9e461293ae243a1ff813a680a4f5f8fb9
Docker info
Builders list
Configuration
https://github.com/osteele/gojekyll/blob/main/Dockerfile, running https://github.com/osteele/gojekyll/blob/main/release.sh#L3
Build logs
Additional info
No response