jdwolk

I just tried updating the Realtek R8168\R8111 driver per this linked forum thread. No difference, I still can't `docker login` or `docker run hello-world` when docker is enabled and I can't pull down any docker images through the web UI. I have 2 days left in my trial license and I will not be able to buy unless I can get docker working.

I'm hoping to get some help on this issue before my trial license runs out in 13 days; otherwise I can't see myself purchasing since everything I want to do will require docker. Some new observations: `docker run --network <X> hello-world` will not work for any value of X I've tried, ie `host` or `bridge`. Using `--dns 8.8.8.8` likewise does nothing. It still times out trying to fetch the container. I've tried `ping`ing from various interfaces and the only one that seems to work is `br0`: ``` root@Homebase:~# ifconfig bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 ether 00:d0:b4:02:1f:84 txqueuelen 1000 (Ethernet) RX packets 61428 bytes 11568043 (11.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37602 bytes 32347951 (30.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.200 netmask 255.255.255.0 broadcast 0.0.0.0 ether 00:d0:b4:02:1f:84 txqueuelen 1000 (Ethernet) RX packets 49980 bytes 9084518 (8.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37602 bytes 32347951 (30.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:49:2c:ae:83 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:d0:b4:02:1f:84 txqueuelen 1000 (Ethernet) RX packets 52755 bytes 10309977 (9.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37602 bytes 32347951 (30.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:d0:b4:02:1f:84 txqueuelen 1000 (Ethernet) RX packets 8673 bytes 1258066 (1.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 6 bytes 234 (234.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6 bytes 234 (234.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Homebase:~# ping -I bond0 google.com ping: Warning: source address might be selected on device other than: bond0 PING google.com (142.250.217.78) from 192.168.1.200 bond0: 56(84) bytes of data. ^C --- google.com ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7195ms root@Homebase:~# ping -I br0 google.com PING google.com (142.251.215.238) from 192.168.1.200 br0: 56(84) bytes of data. 64 bytes from sea09s35-in-f14.1e100.net (142.251.215.238): icmp_seq=1 ttl=58 time=11.4 ms 64 bytes from sea09s35-in-f14.1e100.net (142.251.215.238): icmp_seq=2 ttl=58 time=10.6 ms 64 bytes from sea09s35-in-f14.1e100.net (142.251.215.238): icmp_seq=3 ttl=58 time=10.4 ms ^C --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 10.443/10.825/11.447/0.443 ms root@Homebase:~# ping -I docker0 google.com PING google.com (142.251.215.238) from 172.17.0.1 docker0: 56(84) bytes of data. ^C --- google.com ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7202ms pipe 4 root@Homebase:~# ping -I eth0 google.com ping: Warning: source address might be selected on device other than: eth0 PING google.com (142.251.215.238) from 192.168.1.200 eth0: 56(84) bytes of data. ^C --- google.com ping statistics --- 7 packets transmitted, 0 received, 100% packet loss, time 6123ms root@Homebase:~# ping -I eth1 google.com ping: Warning: source address might be selected on device other than: eth1 PING google.com (142.251.33.78) from 192.168.1.200 eth1: 56(84) bytes of data. ^C --- google.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3107ms ```

Bump

Don’t know if this is at all related but after reading around in the forums it seems like my NIC (Realtek RTL8111H) could be somewhat problematic? Here’s the mobo I’m using: https://www.amazon.com/gp/aw/d/B0CRB225KX?psc=1&ref=ppx_pop_mob_b_asin_title I found this plugin for some Realtek drivers: To be clear: I haven’t installed these yet by hand or anything. And I figure if it _were_ a driver issue I wouldn’t have any connection _at all_ whether or not docker was running. Just hoping more context is more helpful to find a fix; kind of grasping at straws here and no idea if this is the right direction. Thanks again

Hi, I seem to have a near identical problem to this post from 2019: I also have 2 NICs but haven't yet tried disabling one in BIOS like OP did. Completely new Unraid installation. I can ping arbitrary websites when docker is on or off, but with docker on I can't pull images and `docker login` at CLI times out (`docker login` will complete successfully when docker is off). I've similarly tried disabling bonding, changing bonding mode etc. I have no proxys enabled that I'm aware of. I've tried Google DNS servers (8.8.8.8, 8.8.4.4) as well as my router's original DNS servers to the same effect. The issue persists across restarts. Appreciate any help, thanks homebase-diagnostics-20240322-2009.zip