InContainer fails to check on a GCP pod

[D3Hunter]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

[root@tc-tidb-0 /]# cat /proc/1/cgroup
0::/
[root@tc-tidb-0 /]# cat /proc/1/mountinfo
2849 2619 0:283 / / rw,relatime master:665 - overlay overlay rw,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/195/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/194/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/193/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/192/fs:/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/191/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/218/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/218/work
2850 2849 0:285 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
2851 2849 0:286 / /dev rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
2852 2851 0:287 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620,ptmxmode=666
2853 2851 0:258 / /dev/mqueue rw,nosuid,nodev,noexec,relatime - mqueue mqueue rw
2854 2849 0:263 / /sys ro,nosuid,nodev,noexec,relatime - sysfs sysfs ro
2855 2854 0:25 / /sys/fs/cgroup ro,nosuid,nodev,noexec,relatime - cgroup2 cgroup rw
2856 2849 0:248 / /etc/podinfo ro,relatime - tmpfs tmpfs rw,size=60145236k
2857 2849 8:1 /var/lib/kubelet/pods/abf065ee-34b7-46d7-8264-0bece3d7e8e7/volumes/kubernetes.io~configmap/config /etc/tidb ro,relatime - ext4 /dev/sda1 rw,commit=30
2858 2849 8:1 /var/lib/kubelet/pods/abf065ee-34b7-46d7-8264-0bece3d7e8e7/etc-hosts /etc/hosts rw,relatime - ext4 /dev/sda1 rw,commit=30
2859 2851 8:1 /var/lib/kubelet/pods/abf065ee-34b7-46d7-8264-0bece3d7e8e7/containers/tidb/dd4a6152 /dev/termination-log rw,relatime - ext4 /dev/sda1 rw,commit=30
2860 2849 8:1 /var/lib/containerd/io.containerd.grpc.v1.cri/sandboxes/f1a400276ec5a94230956bdb3f022982bb230e587cc0d78d59c7c4fe5cf445a6/hostname /etc/hostname rw,nosuid,nodev,relatime - ext4 /dev/sda1 rw,commit=30
2861 2849 8:1 /var/lib/containerd/io.containerd.grpc.v1.cri/sandboxes/f1a400276ec5a94230956bdb3f022982bb230e587cc0d78d59c7c4fe5cf445a6/resolv.conf /etc/resolv.conf rw,nosuid,nodev,relatime - ext4 /dev/sda1 rw,commit=30
2862 2851 0:255 / /dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw,size=65536k
2863 2849 8:1 /var/lib/kubelet/pods/abf065ee-34b7-46d7-8264-0bece3d7e8e7/volumes/kubernetes.io~configmap/startup-script /usr/local/bin ro,relatime - ext4 /dev/sda1 rw,commit=30
2864 2849 8:16 / /var/lib/tidb/log rw,relatime - ext4 /dev/sdb rw
2865 2849 0:249 / /run/secrets/kubernetes.io/serviceaccount ro,relatime - tmpfs tmpfs rw,size=60145236k
2620 2850 0:285 /bus /proc/bus ro,nosuid,nodev,noexec,relatime - proc proc rw
2621 2850 0:285 /fs /proc/fs ro,nosuid,nodev,noexec,relatime - proc proc rw
2622 2850 0:285 /irq /proc/irq ro,nosuid,nodev,noexec,relatime - proc proc rw
2623 2850 0:285 /sys /proc/sys ro,nosuid,nodev,noexec,relatime - proc proc rw
2624 2850 0:285 /sysrq-trigger /proc/sysrq-trigger ro,nosuid,nodev,noexec,relatime - proc proc rw
2625 2850 0:288 / /proc/acpi ro,relatime - tmpfs tmpfs ro
2626 2850 0:286 /null /proc/kcore rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
2627 2850 0:286 /null /proc/keys rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
2628 2850 0:286 /null /proc/timer_list rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755
2629 2850 0:289 / /proc/scsi ro,relatime - tmpfs tmpfs ro
2630 2854 0:290 / /sys/firmware ro,relatime - tmpfs tmpfs ro

2. What did you expect to see? (Required)

true
and log contains use cgroup memory hook because TiDB is in the container

3. What did you see instead (Required)

false
logs contains this

2024-03-11 13:36:26 (UTC+08:00)TiDB tc-tidb-0.tc-tidb-peer.gsort-import-gcp-tps-7500323-1-546.svc:4000[meminfo.go:196] ["use physical memory hook"] [cgroupMemorySize=68719476736] [physicalMemorySize=67536244736]

4. What is your TiDB version? (Required)

master