What is "setting cgroup item for the container failed" in lxd.log

I am planning to create a Kubernetes cluster using LXD.
If you look at lxd.log in the “/var/snap/lxd/common/lxd/logs” directory during the LXC container creation process, the following is output.

time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8m value=“179,19,230,28,343,351,364,49”
time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8m1 value=“15,298”
time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8w1 value=“146,199,296,361”
time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8w2 value=“337,344”
time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8w3 value=“102,300”
time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8w4 value=“177,204”
time=“2023-11-13T15:54:28+09:00” level=error msg=“balance: Unable to set cpuset” err=“setting cgroup item for the container failed” name=k8w5 value=“280,52”

This log occurs when a container is created (started) or stopped.
The profile used when running this container is as follows:

config:
limits.cpu: “2”
limits.memory: 2GB
limits.memory.swap: “false”
linux.kernel_modules: ip_tables,ip6_tables,nf_nat,overlay,br_netfilter
raw.lxc: “lxc.apparmor.profile=unconfined\nlxc.cap.drop= \nlxc.cgroup.devices.allow=a\nlxc.mount.auto=proc:rw
sys:rw\nlxc.mount.entry = /dev/kmsg dev/kmsg none defaults,bind,create=file”
security.nesting: “true”
security.privileged: “true”
description: LXD profile for Kubernetes
devices:
eth0:
name: eth0
nictype: bridged
parent: lxdbr0
type: nic
root:
path: /
pool: dir
type: disk
name: k8s

Although this log does not cause any problems during the container execution process, I would like to know why this is happening.