Containerd filling messages log file with mount: Succeeded messages

Kubernetes version: 1.20
Cloud being used: bare-metal
Installation method: dnf install
Host OS: Centos 8
CNI and version: Calico
CRI and version: containerd://1.4.3

/var/log/messages getting filled with following:
Dec 29 09:44:06 nalshsvrk8ss04 systemd[83181]: run-containerd-runc-k8s.io-22fe83b00cd57145b127f591708c8766e0bbb3901dbd6df5eeceb84820f9090d-runc.zjukEa.mount: Succeeded.

What cgroup driver are you using? I recall an issue similar to this if it was set to cgroupfs when it should be set to systemd.

I set it to use systemd based on the steps I saw:

grep -i cgroup /etc/containerd/config.toml
[cgroup]
systemd_cgroup = false
disable_cgroup = false
SystemdCgroup = true

      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
        SystemdCgroup = true

Could you double check kubelet and make sure its configured to use it?

It should… Was part of my configuration during kubeadm init…

cat kubeadm_config.yaml

apiVersion: kubelet.config.k8s.io/v1beta1

kind: KubeletConfiguration

cgroupDriver: systemd

# grep cgroupDriver /var/lib/kubelet/config.yaml
cgroupDriver: systemd

hm, don’t know then =/ the cgroup driver was my best guess on that one.

So I am just SOL?

Any suggestions as to where else I can look? I also set Debug to warn instead of debug in the config.toml, but that did not seem to help

[debug]
address = “”
uid = 0
gid = 0
level = “warn”