Timeline for docker interface tears down wifi internet
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2021 at 15:49 | vote | accept | TPPZ | ||
| May 5, 2021 at 13:25 | answer | added | TPPZ | timeline score: 6 | |
| May 5, 2021 at 13:06 | comment | added | ron |
fwiw, running nvidia-docker on rhel 7.9 and while we do not have wifi hardware in our server the 1gbps interface continued to work with zero issues once we installed docker and had it running. However the addition of the docker0: network interface messed up some of our flexlm based software licenses we had on this server... i.e any license that works off network mac address(es) especially the ones that only recognize the first interface such as eth0
|
|
| May 5, 2021 at 12:54 | comment | added | A.B | The problem is not Docker. It's your network manager that detects an interface and tries to configure it. This network manager is wrong and should ignore the interface: bridge ports must never receive an address | |
| May 5, 2021 at 12:33 | comment | added | TPPZ |
Yes it appears as a bridge slave. I found out 169.254.0.0/16 means IPv4LL (link-local) and yes vethf6c1790 appears to have 169.254.198.92 which gets in the middle when a Docker container is running. My wlp2s0 network interface (WiFi) gets assigned a local IP via DHCP by my router - if that's what you mean? My router is somehow assigning a LL IP to the bridge port as well? I struggle to follow - however, my docker installation is the usual one, no custom changes or extra configuration.
|
|
| May 5, 2021 at 12:18 | comment | added | A.B |
docker0 is the bridge interface. vethf6c1790 is the bridge port interface. Don't confuse them. Or maybe it's not in your setup. Check: ip link show type bridge_slave . Does vethf6c1790 appear?
|
|
| May 5, 2021 at 12:18 | comment | added | TPPZ |
docker0 has always had an IP address e.g. 172.17.0.1 (I checked with ifconfig), that's the way I can find where containers listen to e.g. HTTP ports. I am not sure I get the context here, I am not familiar with bridge networks from a practical point of view. Where should I look, what commands or concepts should I research?
|
|
| May 5, 2021 at 12:14 | comment | added | A.B | Among other things, it appears the bridge port interface is configured with an IP address, maybe by a DHCP client (which fails and uses IPv4LL): that's should not be done. | |
| May 5, 2021 at 12:12 | history | edited | TPPZ | CC BY-SA 4.0 |
added 532 characters in body
|
| May 5, 2021 at 12:05 | comment | added | A.B |
Did you try reaching Internet with an IP, like pinging a "famous" IP like 1.1.1.1 or 8.8.8.8, to check it's not just name resolution. Can you also give the result before failure and during failure of ip route get 1.1.1.1 ?
|
|
| May 5, 2021 at 8:02 | history | edited | TPPZ | CC BY-SA 4.0 |
added 512 characters in body
|
| May 5, 2021 at 7:52 | history | edited | TPPZ | CC BY-SA 4.0 |
added 512 characters in body
|
| May 4, 2021 at 16:01 | history | edited | TPPZ | CC BY-SA 4.0 |
added 207 characters in body
|
| May 4, 2021 at 15:48 | history | asked | TPPZ | CC BY-SA 4.0 |