June 19, 20242 yr Hello folks Long time user of Unraid here. I recently moved my disks and USB drive to a new "server" (i5-14400, 64GB RAM). Since moving, at seemingly random times and every 3 to 4 days, I get the kernel panic attached. I have 14 docker containers running in "bridge" mode. Another 1 docker in the br0 bridge network (SWAG) so it has it's own IP on my home network. And 1 docker as host (Home Assistant). I also have 3 virtual machines all on br0 network (virtio-net adapter) with their own IP on my home network. ChatGPT tells me it could be network related but I have no idea. I remember reading about issues with bridge networks in docker and the macvlan stuff. But never actually found a fix. Unraid 6.12.10 Docker 24.0.9 Libvert 8.7.0 QEMU 7.2.0 Any help or feedback is greatly appreciated! Edited June 19, 20242 yr by Piglet7489 added versions
June 19, 20242 yr Community Expert 6 minutes ago, Piglet7489 said: Long time user of Unraid here Attach Diagnostics to your NEXT post in this thread. 6 minutes ago, Piglet7489 said: issues with bridge networks in docker and the macvlan stuff. But never actually found a fix. https://docs.unraid.net/unraid-os/release-notes/6.12.0/#call-traces-related-to-macvlan
June 20, 20242 yr Community Expert Solution Change to ipvlan or if you really need macvlan disable bridging.
June 20, 20242 yr Author Diagnostics attached Okay so I switched to IPVLAN and all works now. Not sure why I ever went to MACVLAN in the first place? I understand it allows physical network access but besides UniFi, what containers would need that function? venus-diagnostics-20240620-1827.zip
June 20, 20242 yr Community Expert It's the same for most containers, some routers don't work well with ipvlan, that's the main use case for macvlan.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.