Why does Docker keep spamming dmesg/syslog after upgrade?

Question

Docker

After updating via apt-get upgrade, br-**** veth**** interfaces with container names appeared, and dmesg/syslog is constantly updated with the following messages:

[4221489.025461] vethbc187bc: renamed from eth0
[4221489.110611] br-ed80aadbb5d1: port 3(veth0a0f385) entered disabled state
[4221489.114478] device veth0a0f385 left promiscuous mode
[4221489.114676] br-ed80aadbb5d1: port 3(veth0a0f385) entered disabled state
[4221489.232189] br-ed80aadbb5d1: port 3(veth6ea6739) entered blocking state
[4221489.232526] br-ed80aadbb5d1: port 3(veth6ea6739) entered disabled state
[4221489.233043] device veth6ea6739 entered promiscuous mode
[4221489.234018] br-ed80aadbb5d1: port 3(veth6ea6739) entered blocking state
[4221489.237627] br-ed80aadbb5d1: port 3(veth6ea6739) entered forwarding state
[4221489.585818] eth0: renamed from vethe43a37e
[4221489.621854] IPv6: ADDRCONF(NETDEV_CHANGE): veth6ea6739: link becomes ready
[4221590.950728] br-ed80aadbb5d1: port 3(veth6ea6739) entered disabled state
[4221590.952862] vethe43a37e: renamed from eth0
[4221591.040281] br-ed80aadbb5d1: port 3(veth6ea6739) entered disabled state
[4221591.045233] device veth6ea6739 left promiscuous mode
[4221591.045491] br-ed80aadbb5d1: port 3(veth6ea6739) entered disabled state
[4221591.145176] br-ed80aadbb5d1: port 3(veth1c6f103) entered blocking state
[4221591.145714] br-ed80aadbb5d1: port 3(veth1c6f103) entered disabled state
[4221591.146425] device veth1c6f103 entered promiscuous mode
[4221591.146985] br-ed80aadbb5d1: port 3(veth1c6f103) entered blocking state
[4221591.150098] br-ed80aadbb5d1: port 3(veth1c6f103) entered forwarding state
[4221591.524839] eth0: renamed from veth558468b
[4221591.556799] IPv6: ADDRCONF(NETDEV_CHANGE): veth1c6f103: link becomes ready

Is this normal behavior or is something wrong? Personally, it doesn't seem normal to me, because there is spam in dmesg.

docker info

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)

Server:
 Containers: 25
  Running: 22
  Paused: 0
  Stopped: 3
 Images: 23
 Server Version: 19.03.14
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e25210fe30a0a703442421b0f60afac609f950a3
 runc version: v1.0.1-0-g4144b63
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.0-77-generic
 Operating System: Ubuntu 20.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 31.27GiB
 Name: XeonServer
 ID: YVEP:AF2N:EOA3:JU7I:NO5N:KV2L:TNWR:5KDX:J3U4:3EH7:ROYM:KC2T
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false