貌似遇到了一个docker 2014年以来就有的大神级大坑，大佬们怎么解决？

pr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered blocking state
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered disabled state
Apr 19 21:48:39 k8s-master01 kernel: device veth7a384b6 entered promiscuous mode
Apr 19 21:48:39 k8s-master01 kernel: IPv6: ADDRCONF(NETDEV_UP): veth7a384b6: link is not ready
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered blocking state
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered forwarding state
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered disabled state
Apr 19 21:48:39 k8s-master01 NetworkManager[527]: <info>  [1681912119.0596] manager: (veth6247d00): new Veth device (/org/freedesktop/NetworkManager/Devices/736)
Apr 19 21:48:39 k8s-master01 NetworkManager[527]: <info>  [1681912119.0603] manager: (veth7a384b6): new Veth device (/org/freedesktop/NetworkManager/Devices/737)
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.107854447+08:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.107951077+08:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.107961794+08:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.108169610+08:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/c8dfca4e2c0cad99d7d5195b693759e672b3f9f0c4c93ab9805c0958265d4bf9 pid=9754 runtime=io.containerd.runc.v2
Apr 19 21:48:39 k8s-master01 kernel: IPVS: Creating netns size=2048 id=49
Apr 19 21:48:39 k8s-master01 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 19 21:48:39 k8s-master01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 19 21:48:39 k8s-master01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7a384b6: link becomes ready
Apr 19 21:48:39 k8s-master01 NetworkManager[527]: <info>  [1681912119.2471] device (veth7a384b6): carrier: link connected
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered blocking state
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered forwarding state
Apr 19 21:48:39 k8s-master01 NetworkManager[527]: <info>  [1681912119.2514] device (docker0): carrier: link connected
Apr 19 21:48:39 k8s-master01 dockerd: time="2023-04-19T21:48:39.547337727+08:00" level=info msg="ignoring event" container=c8dfca4e2c0cad99d7d5195b693759e672b3f9f0c4c93ab9805c0958265d4bf9 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.547539758+08:00" level=info msg="shim disconnected" id=c8dfca4e2c0cad99d7d5195b693759e672b3f9f0c4c93ab9805c0958265d4bf9
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.547578914+08:00" level=warning msg="cleaning up after shim disconnected" id=c8dfca4e2c0cad99d7d5195b693759e672b3f9f0c4c93ab9805c0958265d4bf9 namespace=moby
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.547591062+08:00" level=info msg="cleaning up dead shim"
Apr 19 21:48:39 k8s-master01 containerd: time="2023-04-19T21:48:39.557980137+08:00" level=warning msg="cleanup warnings time=\"2023-04-19T21:48:39+08:00\" level=info msg=\"starting signal loop\" namespace=moby pid=10225 runtime=io.containerd.runc.v2\n"
Apr 19 21:48:39 k8s-master01 kernel: docker0: port 1(veth7a384b6) entered disabled state
Apr 19 21:48:39 k8s-master01 NetworkManager[527]: <info>  [1681912119.5750] manager: (veth6247d00): new Veth device (/org/freedesktop/NetworkManager/Devices/738)