docker get veth network card auto-generated every 5 minutes

[Larkdone]

Hi all, I've got installed the docker package (both in stable and latest version) in a fresh machine, when I get one of my container started (it use the default bridge network), I've found there's a bunch of system log here:

Mar 16 15:15:26 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered blocking state
Mar 16 15:15:26 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered disabled state
Mar 16 15:15:26 myhost kernel: device veth9e83f96 entered promiscuous mode
Mar 16 15:15:26 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered blocking state
Mar 16 15:15:26 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered forwarding state
Mar 16 15:15:26 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered disabled state
Mar 16 15:15:27 myhost kernel: cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
Mar 16 15:15:28 myhost kernel: eth0: renamed from veth34c836d
Mar 16 15:15:28 myhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9e83f96: link becomes ready
Mar 16 15:15:28 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered blocking state
Mar 16 15:15:28 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered forwarding state
Mar 16 15:15:28 myhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-9abbab7f260b: link becomes ready
Mar 16 15:20:29 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered disabled state
Mar 16 15:20:29 myhost kernel: veth34c836d: renamed from eth0
Mar 16 15:20:29 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered disabled state
Mar 16 15:20:29 myhost kernel: device veth9e83f96 left promiscuous mode
Mar 16 15:20:29 myhost kernel: br-9abbab7f260b: port 1(veth9e83f96) entered disabled state
Mar 16 15:20:30 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered blocking state
Mar 16 15:20:30 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered disabled state
Mar 16 15:20:30 myhost kernel: device vetha17d300 entered promiscuous mode
Mar 16 15:20:30 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered blocking state
Mar 16 15:20:30 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered forwarding state
Mar 16 15:20:30 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered disabled state
Mar 16 15:20:31 myhost kernel: eth0: renamed from veth8ed92e1
Mar 16 15:20:31 myhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha17d300: link becomes ready
Mar 16 15:20:31 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered blocking state
Mar 16 15:20:31 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered forwarding state
Mar 16 15:25:32 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered disabled state
Mar 16 15:25:32 myhost kernel: veth8ed92e1: renamed from eth0
Mar 16 15:25:32 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered disabled state
Mar 16 15:25:32 myhost kernel: device vetha17d300 left promiscuous mode
Mar 16 15:25:32 myhost kernel: br-9abbab7f260b: port 1(vetha17d300) entered disabled state
Mar 16 15:25:33 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered blocking state
Mar 16 15:25:33 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered disabled state
Mar 16 15:25:33 myhost kernel: device vethdf64b15 entered promiscuous mode
Mar 16 15:25:33 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered blocking state
Mar 16 15:25:33 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered forwarding state
Mar 16 15:25:33 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered disabled state
Mar 16 15:25:34 myhost kernel: eth0: renamed from veth3c68116
Mar 16 15:25:34 myhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethdf64b15: link becomes ready
Mar 16 15:25:34 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered blocking state
Mar 16 15:25:34 myhost kernel: br-9abbab7f260b: port 1(vethdf64b15) entered forwarding state

=> The interval of the Veth virtual network card get auto-deleted and re-added, is obviously, 5 minutes.

I have another Gentoo machine also, but system was install several months ago (docker package is the current stable version, i got it updated already). That system doesn't generate the above info, it seems.

Could you help check which reason might cause this?
This seems the log would get flushed all over the system log.
Many thanks on this..

------------
Update in 3.19: Get installed in another fresh-install gentoo system, no globle USE flag used or app installed (except docker), this issue stilll occues.
Update in 3.29: I've get issue seems reproduced in Debian 10.8, doesn't know if this due to the upstream or kernel.