[6.12.3] Daily crash

Jul 29 07:31:50 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Jul 29 07:31:50 Tower kernel: ? _raw_spin_unlock+0x14/0x29
Jul 29 07:31:50 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

I switched to ipvlan.  All my containers seem to run fine.  Now we wait......

Now I have a different, but similar crash.  Log attached.

unraid.log

Please post output of:

docker network ls

 

root@Tower:~# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
3072d7630feb   br0       ipvlan    local
27dc2f81b4e6   bridge    bridge    local
1c177321660e   host      host      local
4434f0935c25   none      null      local
1460fa1acee5   wg0       bridge    local
b001f8dbb75d   wg1       bridge    local
root@Tower:~# 

 

Looks OK, just wanted to confirm macvlan was not in use, a user reported it was even  after changing to ipvlan, and the the call trace logged is similar, but in that case don't know what the problem is.

Thanks for the help - in the short term I'll roll back to 6.11.5 and keep an eye on the forums.

might be similar to what I observed -

I had to disable an additional thing and add some arguments to containers but I haven't had a single issue since, the only thing to blame as far as I can tell was macvlan driver. I think you also need to disable "Host access to custom networks".

Could someone explain why the switch from macvlan to ipvlan is necessary after upgrading to 6.12.x? Does anyone know what is happening with this bug? I went back to 6.11.x on all of the servers that I manage but am waiting to upgrade until I have some confirmation that this is fixed.

On 8/8/2023 at 6:34 PM, Shagon said:

I think you also need to disable "Host access to custom networks".

 

Isn't this needed for Wireguard access to docker containers?

Anyone upgrade to 6.12.4 to see if this crash as gone away?