Dev Container: cgfsng error

Incus
1

I am currently developing inside a dev container built out of the Dockerfile provided within the project repo. When I attempt to launch a container such as:

incus launch images:debian/13 c1 --network br-test

I end up with the following errors in my log:

lxc c1 20250516223821.870 ERROR    cgfsng - ../src/lxc/cgroups/cgfsng.c:__cgfsng_delegate_controllers:3341 - Device or resource busy - Could not enable "+cpuset +cpu +io +memory +hugetlb +pids +rdma +misc" controllers in the unified cgroup 10

lxc c1 20250516223821.902 ERROR    cgfsng - ../src/lxc/cgroups/cgfsng.c:__cgfsng_delegate_controllers:3341 - Device or resource busy - Could not enable "+cpuset +cpu +io +memory +hugetlb +pids +rdma +misc" controllers in the unified cgroup 10

lxc c1 20250516223821.902 WARN     cgfsng - ../src/lxc/cgroups/cgfsng.c:fchowmodat:1619 - No such file or directory - Failed to fchownat(16, memory.oom.group, 65536, 0, AT_EMPTY_PATH | AT_SYMLINK_NOFOLLOW )

Within the dev container environment the cgroup.controllers and cgroup.subtree_control file is present, but there are no entries inside.

This is my host setup:

System:
Kernel: 5.15.0-140-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy

I would like to know which specific boot configuration settings in my kernel I should be checking for. And then is it possible have CGroup controllers inside a Docker container and if so how?

2

In a similar environment, I’ve had to make sure the dev container had something like this:


  "runArgs": [
    "--privileged",
    "--cap-add=SYS_PTRACE",
    "--security-opt", "seccomp=unconfined",
    "--cgroupns=host",
    "--pid=host",
    "--volume", "/dev:/dev",
    "--volume", "/lib/modules:/lib/modules:ro"
1 Like