Open byteshiva opened 7 months ago
Description: When running docker info | grep cgroupos, a warning is displayed indicating the absence of cpuset support:
docker info | grep cgroupos
WARNING: No cpuset support
Upon further investigation, it seems that cgroup2 is mounted:
mount | grep cgroup2 cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
Furthermore, examining the content of /proc/cgroups, it shows that cpuset is enabled:
/proc/cgroups
| subsys_name | hierarchy | num_cgroups | enabled | |-------------|-----------|-------------|---------| | cpuset | 0 | 112 | 1 | | cpu | 0 | 112 | 1 | | cpuacct | 0 | 112 | 1 | | blkio | 0 | 112 | 1 | | memory | 0 | 112 | 1 | | devices | 0 | 112 | 1 | | freezer | 0 | 112 | 1 | | net_cls | 0 | 112 | 1 | | perf_event | 0 | 112 | 1 | | net_prio | 0 | 112 | 1 | | hugetlb | 0 | 112 | 1 | | pids | 0 | 112 | 1 | | rdma | 0 | 112 | 1 | | misc | 0 | 112 | 1 | | debug | 0 | 112 | 1 |
This table provides a clear overview of the subsystem names, hierarchy, number of cgroups, and whether they are enabled.
Despite cpuset being enabled in the cgroups hierarchy, Docker still reports the absence of cpuset support.
This discrepancy raises concerns about Docker's performance and behavior, especially for containers relying on cpuset functionalities.
Could you please advise on how to resolve this inconsistency and ensure optimal Docker performance in this environment?
Description: When running
docker info | grep cgroupos
, a warning is displayed indicating the absence of cpuset support:Upon further investigation, it seems that cgroup2 is mounted:
Furthermore, examining the content of
/proc/cgroups
, it shows that cpuset is enabled:This table provides a clear overview of the subsystem names, hierarchy, number of cgroups, and whether they are enabled.
Despite cpuset being enabled in the cgroups hierarchy, Docker still reports the absence of cpuset support.
This discrepancy raises concerns about Docker's performance and behavior, especially for containers relying on cpuset functionalities.
Could you please advise on how to resolve this inconsistency and ensure optimal Docker performance in this environment?