Kernel panics, I believe related to Bridge in Docker

[geiserx]

This is how a typical syslog looks like everytime:

 

Jul  1 13:26:43 WatchTower kernel: device veth2c79359 entered promiscuous mode
Jul  1 13:26:43 WatchTower kernel: eth0: renamed from vethe879fce
Jul  1 13:26:44 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2c79359: link becomes ready
Jul  1 13:26:44 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered blocking state
Jul  1 13:26:44 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered forwarding state
Jul  1 13:26:45 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered disabled state
Jul  1 13:26:45 WatchTower kernel: vethe879fce: renamed from eth0
Jul  1 13:26:45 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered disabled state
Jul  1 13:26:45 WatchTower kernel: device veth2c79359 left promiscuous mode
Jul  1 13:26:45 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered disabled state
Jul  1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered blocking state
Jul  1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state
Jul  1 13:27:45 WatchTower kernel: device veth0ed10ae entered promiscuous mode
Jul  1 13:27:45 WatchTower kernel: eth0: renamed from veth95735b7
Jul  1 13:27:45 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0ed10ae: link becomes ready
Jul  1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered blocking state
Jul  1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered forwarding state
Jul  1 13:27:47 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state
Jul  1 13:27:47 WatchTower kernel: veth95735b7: renamed from eth0
Jul  1 13:27:47 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state
Jul  1 13:27:47 WatchTower kernel: device veth0ed10ae left promiscuous mode
Jul  1 13:27:47 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered blocking state
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state
Jul  1 13:28:47 WatchTower kernel: device vethf9ef870 entered promiscuous mode
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered blocking state
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered forwarding state
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state
Jul  1 13:28:47 WatchTower kernel: eth0: renamed from vethf1f9499
Jul  1 13:28:47 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf9ef870: link becomes ready
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered blocking state
Jul  1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered forwarding state
Jul  1 13:28:48 WatchTower kernel: vethf1f9499: renamed from eth0
Jul  1 13:28:48 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state
Jul  1 13:28:48 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state
Jul  1 13:28:48 WatchTower kernel: device vethf9ef870 left promiscuous mode
Jul  1 13:28:48 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state
Jul  1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered blocking state
Jul  1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state
Jul  1 13:29:48 WatchTower kernel: device veth7372316 entered promiscuous mode
Jul  1 13:29:48 WatchTower kernel: eth0: renamed from veth1f254a4
Jul  1 13:29:48 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7372316: link becomes ready
Jul  1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered blocking state
Jul  1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered forwarding state
Jul  1 13:29:50 WatchTower kernel: veth1f254a4: renamed from eth0
Jul  1 13:29:50 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state
Jul  1 13:29:50 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state
Jul  1 13:29:50 WatchTower kernel: device veth7372316 left promiscuous mode
Jul  1 13:29:50 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state
Jul  1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered blocking state
Jul  1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state
Jul  1 13:30:50 WatchTower kernel: device veth6e4aa48 entered promiscuous mode
Jul  1 13:30:50 WatchTower kernel: eth0: renamed from veth378aea0
Jul  1 13:30:50 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6e4aa48: link becomes ready
Jul  1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered blocking state
Jul  1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered forwarding state
Jul  1 13:30:52 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state
Jul  1 13:30:52 WatchTower kernel: veth378aea0: renamed from eth0
Jul  1 13:30:52 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state
Jul  1 13:30:52 WatchTower kernel: device veth6e4aa48 left promiscuous mode
Jul  1 13:30:52 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state

If I inspect the link, it belongs to Prometheus and all the exporters I've configured. If I turn it off, it stops.

I suspect this is causing frequent kernel panics, but I can't prove it. Nevertheless, could anyone please tell me what's going on internally?

[JorgeB]

You likely have a container constantly restarting, see if you can find which one by looking at their uptimes.