mounting "cgroup" to rootfs at "/sys/fs/cgroup" caused: stat no such file or directory

I use the oci worker of buildkit to build the image, and I encounter the following error, which is an occasional error.

#10 [builder 4/4] RUN go build main.go
#10 0.143 container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "cgroup" to rootfs at "/sys/fs/cgroup" caused: stat /sys/fs/cgroup/freezer/kubepods-burstable-pode4fa6d79_1abb_4e77_9f6d_4e62ff0d3437.slice:cri-containerd:7c1fc613a2b03bb85b958931fa53a0bfc422cdbde70eaa2b15cbf71485c1c4ec/buildkit/r8wym59fjeuwv89y521xsiqza: no such file or directory
#10 ERROR: process "/bin/sh -c go build main.go" did not complete successfully: exit code: 1
------
 > [builder 4/4] RUN go build main.go:
#10 0.143 container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "cgroup" to rootfs at "/sys/fs/cgroup" caused: stat /sys/fs/cgroup/freezer/kubepods-burstable-pode4fa6d79_1abb_4e77_9f6d_4e62ff0d3437.slice:cri-containerd:7c1fc613a2b03bb85b958931fa53a0bfc422cdbde70eaa2b15cbf71485c1c4ec/buildkit/r8wym59fjeuwv89y521xsiqza: no such file or directory

version

bash-5.1# buildkit-runc --version
runc version v1.0.2
spec: 1.0.2-dev
go: go1.17.13
libseccomp: 2.5.2

Under what circumstances will this problem occur?

thanks！

Start with the reported runc paths container_linux.go:380, process_linux.go:545, and rootfs_linux.go:76, then inspect how the buildkit OCI worker mounts cgroup at /sys/fs/cgroup. Reproduce the intermittent failure with runc v1.0.2 in the reported Kubernetes/containerd setup and document the circumstances that trigger the missing freezer path.