I've started to have a few incidents where my unraid server just dies and i have to manually reboot it. The GUI dies or the SSH stops responding randomly. But since thursday, I am unable to use my docker containers. I've tried deleting the docker.img without luck so i'll be restoring it once it's back online. I've also tried to turn off vms & docker without luck, it's still starting them.

Here are the diagnostics

 

Not sure what to do, but the GUI is not stable at all, ass it just stops to respond whenever i tried to use it, also, parity is okay as far as i know.

Thanks !

 

logs.zip

Edited December 30, 20232 yr by Tom Morello

First thing:

 

Dec 26 09:40:10 Asgard kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec 26 09:40:10 Asgard kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

 

Then recreate the docker image since it's corrupt, if it's was recreated recently you may have an underlying issue causing that.

Thanks, it definitely helped. I also tried restoring the original docker.img with the proper ipvlan configuration, and it's working fine now. Let me ask you a question, though. I forgot that I switched to macvlan after the 6.12.6 update because ipvlan was not allowing me to assign an IP to the container. For example, my Time Machine container previously had the 192.168.1.220 IP assigned, but now it's just acting as a bridge without an assigned IP. Do you know how can i fix that ?

Ipvlan should still allow you to assign an IP to a container, but you can still use macvlan if you really need it, must disable bridging for eth0, see the v6.12.4 release notes.

After switching this time, it allowed me to assign the IP. I am not sure what happened, but now it's working with the assigned IP, as well as with the VLAN and containers. Thank you very much