Docker MTU Issues and Solutions
Fleeting- Référence externe : https://mlohr.com/docker-mtu/
common problem when operating dockers within a virtualization infrastructure is that the network cards provided to virtual machines do not have the default MTU of 1500. This is often the case, for example, when working in a cloud infrastructure (e.g. OpenStack). — https://mlohr.com/docker-mtu/
With the command ip link you can display the locally configured network cards and their MTU:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1454 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether aa:bb:cc:dd:ee:ff brd ff:ff:ff:ff:ff:ff 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether uu:vv:ww:xx:yy:zz brd ff:ff:ff:ff:ff:ff If the outgoing interface (in this case ens3) has an MTU smaller than 1500, some action is required. If it is greater than or equal to 1500, this problem does not apply to you.
create the file /etc/docker/daemon.json with the following content:
{ “mtu”: 1454 }
docker does not check the mtu at startup
The Docker Daemon does not check the MTU of the outgoing connection at startup. Therefore, the value of the Docker MTU is set to 1500
Notes pointant ici
- fix Docker MTU issues and solutions
- fix Docker MTU issues and solutions in actions-runner-controller
- how I debug MTU issues in k3d in docker in earthly in docker in k8s (blog)