TheOgre
Members
-
Joined
-
Last visited
Solutions
-
TheOgre's post in Docker: Error response from daemon: failed to create the ipvlan port: device or resource busy was marked as the answerOkay so, after working on a completely separate project involving a docker networking setting, I ran across something that helped me to resolve this.
TURNS OUT, back in version 6.9.x, there was a docker issue I was having relating to networking, and I had placed a USER SCRIPT to manually add the docker network at boot time. Well, this configuration used a completely different IP range than what the server is using now. I completely forgot about this script existing or to even check for it, so my ENTIRE issue was caused by this rouge script I had placed. After disabling/deleting the script and rebooting, all docker containers boot up perfectly fine!
Turns out, the reason toggling host access and restarting docker worked, it was just deleting the docker network, and recreating it as it was supposed to be. I feel silly but, HEY, IT'S FIXED!
-
TheOgre's post in Issue with networking, eth0 non-functional was marked as the answerOkay so, after following your suggestion @Squid, it made me think to try a Live ISO and see if the network issues persists with a known working live drive. Well, it did not, and this led me down the road of trying the network stuff again. Turns out, I have a malfunctioning network switch. It seems to be passing SOME requests, but dropping everything else. After running a very long cable to the main ap, everything works just fine in unraid.
Thanks for the nudge that got me to the solution!!