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
Executing the CodeQL GitHub Action within a Docker container results in the detection of only a single CPU, due to the /sys/fs/cgroup/cpuset.cpus file being empty.
#2139
Closed
kouberl-bosch opened this issue
Feb 14, 2024
· 3 comments
· Fixed by #2151
when using the github action in a container action with a docker image which has cgroup v2 it cannot be run multithreaded.
Example output:
While resolving threads, found a cgroup CPUs file with 32 CPUs in /sys/fs/cgroup/cpuset.cpus.effective.
While resolving threads, found a cgroup CPUs file with 1 CPUs in /sys/fs/cgroup/cpuset.cpus.
If "cpuset.cpus" is empty, the "cpuset.cpus.effective" file shows
all the CPUs from the parent cgroup that can be available to
be used by this cgroup.
Now this lead to a maximum number of 1 CPU.
Relates to #2083
The text was updated successfully, but these errors were encountered:
kouberl-bosch
changed the title
Running codeql-action in container action leads to found only 1 CPU due to empty /sys/fs/cgroup/cpuset.cpus file
Executing the CodeQL GitHub Action within a Docker container results in the detection of only a single CPU, due to the /sys/fs/cgroup/cpuset.cpus file being empty.
Feb 14, 2024
Hello! Thank you for reporting. I can look into this for you as I authored #2083. I'd like to understand why /sys/fs/cgroup/cpuset.cpus is reporting 1 CPU here:
Hi,
when using the github action in a container action with a docker image which has cgroup v2 it cannot be run multithreaded.
Example output:
This happens because at my docker image (ubuntu:22.04) the /sys/fs/cgroup/cpuset.cpus is empty which is legit:
see https://www.kernel.org/doc/Documentation/admin-guide/cgroup-v2.rst
Now this lead to a maximum number of 1 CPU.
Relates to #2083
The text was updated successfully, but these errors were encountered: