You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This test is verifying that the container has the right options set (through docker inspect), but also checks if the cgroup-rules are set within the container by reading /sys/fs/cgroup/devices/devices.list
Unlike cgroups v1, on cgroups v2, there is no file interface, and rules are handled through ebpf, which means that the test will fail because this file is not present.
(...)
Device controller manages access to device files. It includes both creation of new device files (using mknod), and access to the existing device files.
Cgroup v2 device controller has no interface files and is implemented on top of cgroup BPF. To control access to device files, a user may create bpf programs of type BPF_PROG_TYPE_CGROUP_DEVICE and attach them to cgroups with BPF_CGROUP_DEVICE flag. (...)
The text was updated successfully, but these errors were encountered:
See moby/moby#42941 (comment)
This test is verifying that the container has the right options set (through
docker inspect
), but also checks if the cgroup-rules are set within the container by reading/sys/fs/cgroup/devices/devices.list
Unlike cgroups v1, on cgroups v2, there is no file interface, and rules are handled through ebpf, which means that the test will fail because this file is not present.
From the Linux documentation for cgroups v2: https://github.com/torvalds/linux/blob/v5.16/Documentation/admin-guide/cgroup-v2.rst#device-controller
The text was updated successfully, but these errors were encountered: