408 Request Time-out while signing in or pulling an image
This issue was caused by the fact that the MTU on both the ethernet and wifi connection was set to AUTO. The issue can be fixed changing the MTU to 900 using one of the following options:
For each network interface managed by the NetworkManager daemon, a configuration file is created inside the /etc/sysconfig/network-scripts directory. The name of the file is composed by the ifcfg- prefix plus the name of the interface.
We can manually change the NIC configuration files:
sudo vim /etc/sysconfig/network-scripts/ifcfg-[NIC_NAME]
sudo nmcli connection down [NIC_NAME]
sudo nmcli connection up [NIC_NAME]
By running the ip addr command again we can verify the IP has changed:
ip addr | grep [NIC_NAME]
using nmtui:
sudo nmtui
sudo nmcli connection down [NIC_NAME]
sudo nmcli connection up [NIC_NAME]
Usingip link set
ip link list
sudo ip link set wlp2s0 mtu 900
sudo ip link set enp0s31f6 mtu 900
sudo systemctl restart NetworkManager
Container B has not access to Container A and log file error is:
NO ROUTE TO HOST network request from container to...
This was firewall issue in the OS hosting docker. To troubleshoot the issue: 1) Check if the port from container A is accessible from the localhost:
ss | head -1 1.ss -l | grep LISTEN | grep tcp
telnet localhost 2181
check docker logs -f containerA to watch the connection happening
If the connection can happen from the hosting operation system, and not from container B, then it try to temporary disable the firewalld to verify if this fixes the issue.
Add appropriate firewall configuration
# Masquerading allows for docker ingress and egress (this is the juicy bit)
firewall-cmd --zone=public --add-masquerade --permanen
# Reload firewall to apply permanent rules
firewall-cmd --reload
Further information on Docker networking time issue can be found here:
