We have had a similar issue when instance network MTU was 1450 due to VXLAN usage but docker by default creates bridged network with MTU 1500.
Configuring /etc/docker/daemon.json to be like:
{
"mtu": 1400
}
And restarting docker fixed it for us.
Usage of host network also works but it limits docket usage a lot.
For docker-compose use network and define MTU as well, e.g.
2
Answers
Same workaround mentioned by “solvease”(Feb 5 at 8:58) > use ‘–network host’ or ‘network_mode: “host”‘ for docker-compose definition.
We have had a similar issue when instance network MTU was 1450 due to VXLAN usage but docker by default creates bridged network with MTU 1500.
Configuring /etc/docker/daemon.json to be like:
And restarting docker fixed it for us.
Usage of host network also works but it limits docket usage a lot.
For docker-compose use network and define MTU as well, e.g.
This behaviour describe here:
https://mlohr.com/docker-mtu/ and here
https://sylwit.medium.com/how-we-spent-a-full-day-figuring-out-a-mtu-issue-with-docker-4d81fdfe2caf