You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the container, the log of my host OS gets spammed with this error:
kernel: qemubr0: received packet on eth0 with own address as source address (addr:03:42:ab:11:00:02, vlan:0)
From my research this indicates that there is a loop in the LAN somewhere. So this is probably caused by the bridge interface that gets created when starting the container.
Any clues on how to prevent this error from popping up?
The text was updated successfully, but these errors were encountered:
When running the container, the log of my host OS gets spammed with this error:
kernel: qemubr0: received packet on eth0 with own address as source address (addr:03:42:ab:11:00:02, vlan:0)
From my research this indicates that there is a loop in the LAN somewhere. So this is probably caused by the bridge interface that gets created when starting the container.
Any clues on how to prevent this error from popping up?
The text was updated successfully, but these errors were encountered: