How do I check cgroup v2 is installed on my machine?Creating one-time cgroupAdding entire session to a cgroupcgroup memory.usage_in_bytes always zero for some tasksCannot set memory.memsw.limit_in_bytes in cgroup on Ubuntu server using cgmPlace all processes belonging to user in a cgroupCould not find writable mount point for cgroup hierarchy 13 while trying to create cgroupwhat is the effect of setting cpu.cpu_quota_us in cpu cgroup?Is my cgroup overloaded?Using Cgroup inside network namespace?unload a module from another module
Replace character with another only if repeated and not part of a word
Increase performance creating Mandelbrot set in python
Tiptoe or tiphoof? Adjusting words to better fit fantasy races
How to write papers efficiently when English isn't my first language?
How do I extract a value from a time formatted value in excel?
How do scammers retract money, while you can’t?
Is there a korbon needed for conversion?
What is paid subscription needed for in Mortal Kombat 11?
I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?
Roman Numeral Treatment of Suspensions
Two monoidal structures and copowering
Lay out the Carpet
Where does the Z80 processor start executing from?
Did Dumbledore lie to Harry about how long he had James Potter's invisibility cloak when he was examining it? If so, why?
How easy is it to start Magic from scratch?
Is HostGator storing my password in plaintext?
What is the opposite of 'gravitas'?
Valid Badminton Score?
Shortcut for value of this indefinite integral?
Is expanding the research of a group into machine learning as a PhD student risky?
How did Doctor Strange see the winning outcome in Avengers: Infinity War?
Do the temporary hit points from the Battlerager barbarian's Reckless Abandon stack if I make multiple attacks on my turn?
What is the best translation for "slot" in the context of multiplayer video games?
Is oxalic acid dihydrate considered a primary acid standard in analytical chemistry?
How do I check cgroup v2 is installed on my machine?
Creating one-time cgroupAdding entire session to a cgroupcgroup memory.usage_in_bytes always zero for some tasksCannot set memory.memsw.limit_in_bytes in cgroup on Ubuntu server using cgmPlace all processes belonging to user in a cgroupCould not find writable mount point for cgroup hierarchy 13 while trying to create cgroupwhat is the effect of setting cpu.cpu_quota_us in cpu cgroup?Is my cgroup overloaded?Using Cgroup inside network namespace?unload a module from another module
I want to try cgroup v2 but am not sure if it is installed on my linux machine
>> uname -r
4.14.66-041466-generic
Since cgroup v2 is available in 4.12.0-rc5, I assume it should be available in the kernel version I am using.
https://www.infradead.org/~mchehab/kernel_docs/unsorted/cgroup-v2.html
However, it does not seem like my system has cgroup v2 as the memory interface files mentioned in its documentation are not available on my system.
https://www.kernel.org/doc/Documentation/cgroup-v2.txt
It seems like I still have cgroup v1.
/sys/fs/cgroup/memory# ls
cgroup.clone_children memory.kmem.failcnt memory.kmem.tcp.usage_in_bytes memory.memsw.usage_in_bytes memory.swappiness
cgroup.event_control memory.kmem.limit_in_bytes memory.kmem.usage_in_bytes memory.move_charge_at_immigrate memory.usage_in_bytes
cgroup.procs memory.kmem.max_usage_in_bytes memory.limit_in_bytes memory.numa_stat memory.use_hierarchy
cgroup.sane_behavior memory.kmem.slabinfo memory.max_usage_in_bytes memory.oom_control notify_on_release
docker memory.kmem.tcp.failcnt memory.memsw.failcnt memory.pressure_level release_agent
memory.failcnt memory.kmem.tcp.limit_in_bytes memory.memsw.limit_in_bytes memory.soft_limit_in_bytes tasks
memory.force_empty memory.kmem.tcp.max_usage_in_bytes memory.memsw.max_usage_in_bytes memory.stat
Follow-up questions
Thanks Brian for the help. Please let me know if I should be creating a new question but I think it might be helpful to other if I just ask my questions here.
1) I am unable to add cgroup controllers, following the command in the doc
>> echo "+cpu +memory -io" > cgroup.subtree_control
However, I got "echo: write error: Invalid argument". Am I missing a prerequisite to this step?
2) I ran a docker container but the docker daemon log complained about not able to find "/sys/fs/cgroup/cpuset/docker/cpuset.cpus". It seems like docker is still expecting cgroupv1. What is the best way to enable cgroupv2 support on my docker daemon?
docker -v
Docker version 17.09.1-ce, build aedabb7
linux cgroups
add a comment |
I want to try cgroup v2 but am not sure if it is installed on my linux machine
>> uname -r
4.14.66-041466-generic
Since cgroup v2 is available in 4.12.0-rc5, I assume it should be available in the kernel version I am using.
https://www.infradead.org/~mchehab/kernel_docs/unsorted/cgroup-v2.html
However, it does not seem like my system has cgroup v2 as the memory interface files mentioned in its documentation are not available on my system.
https://www.kernel.org/doc/Documentation/cgroup-v2.txt
It seems like I still have cgroup v1.
/sys/fs/cgroup/memory# ls
cgroup.clone_children memory.kmem.failcnt memory.kmem.tcp.usage_in_bytes memory.memsw.usage_in_bytes memory.swappiness
cgroup.event_control memory.kmem.limit_in_bytes memory.kmem.usage_in_bytes memory.move_charge_at_immigrate memory.usage_in_bytes
cgroup.procs memory.kmem.max_usage_in_bytes memory.limit_in_bytes memory.numa_stat memory.use_hierarchy
cgroup.sane_behavior memory.kmem.slabinfo memory.max_usage_in_bytes memory.oom_control notify_on_release
docker memory.kmem.tcp.failcnt memory.memsw.failcnt memory.pressure_level release_agent
memory.failcnt memory.kmem.tcp.limit_in_bytes memory.memsw.limit_in_bytes memory.soft_limit_in_bytes tasks
memory.force_empty memory.kmem.tcp.max_usage_in_bytes memory.memsw.max_usage_in_bytes memory.stat
Follow-up questions
Thanks Brian for the help. Please let me know if I should be creating a new question but I think it might be helpful to other if I just ask my questions here.
1) I am unable to add cgroup controllers, following the command in the doc
>> echo "+cpu +memory -io" > cgroup.subtree_control
However, I got "echo: write error: Invalid argument". Am I missing a prerequisite to this step?
2) I ran a docker container but the docker daemon log complained about not able to find "/sys/fs/cgroup/cpuset/docker/cpuset.cpus". It seems like docker is still expecting cgroupv1. What is the best way to enable cgroupv2 support on my docker daemon?
docker -v
Docker version 17.09.1-ce, build aedabb7
linux cgroups
add a comment |
I want to try cgroup v2 but am not sure if it is installed on my linux machine
>> uname -r
4.14.66-041466-generic
Since cgroup v2 is available in 4.12.0-rc5, I assume it should be available in the kernel version I am using.
https://www.infradead.org/~mchehab/kernel_docs/unsorted/cgroup-v2.html
However, it does not seem like my system has cgroup v2 as the memory interface files mentioned in its documentation are not available on my system.
https://www.kernel.org/doc/Documentation/cgroup-v2.txt
It seems like I still have cgroup v1.
/sys/fs/cgroup/memory# ls
cgroup.clone_children memory.kmem.failcnt memory.kmem.tcp.usage_in_bytes memory.memsw.usage_in_bytes memory.swappiness
cgroup.event_control memory.kmem.limit_in_bytes memory.kmem.usage_in_bytes memory.move_charge_at_immigrate memory.usage_in_bytes
cgroup.procs memory.kmem.max_usage_in_bytes memory.limit_in_bytes memory.numa_stat memory.use_hierarchy
cgroup.sane_behavior memory.kmem.slabinfo memory.max_usage_in_bytes memory.oom_control notify_on_release
docker memory.kmem.tcp.failcnt memory.memsw.failcnt memory.pressure_level release_agent
memory.failcnt memory.kmem.tcp.limit_in_bytes memory.memsw.limit_in_bytes memory.soft_limit_in_bytes tasks
memory.force_empty memory.kmem.tcp.max_usage_in_bytes memory.memsw.max_usage_in_bytes memory.stat
Follow-up questions
Thanks Brian for the help. Please let me know if I should be creating a new question but I think it might be helpful to other if I just ask my questions here.
1) I am unable to add cgroup controllers, following the command in the doc
>> echo "+cpu +memory -io" > cgroup.subtree_control
However, I got "echo: write error: Invalid argument". Am I missing a prerequisite to this step?
2) I ran a docker container but the docker daemon log complained about not able to find "/sys/fs/cgroup/cpuset/docker/cpuset.cpus". It seems like docker is still expecting cgroupv1. What is the best way to enable cgroupv2 support on my docker daemon?
docker -v
Docker version 17.09.1-ce, build aedabb7
linux cgroups
I want to try cgroup v2 but am not sure if it is installed on my linux machine
>> uname -r
4.14.66-041466-generic
Since cgroup v2 is available in 4.12.0-rc5, I assume it should be available in the kernel version I am using.
https://www.infradead.org/~mchehab/kernel_docs/unsorted/cgroup-v2.html
However, it does not seem like my system has cgroup v2 as the memory interface files mentioned in its documentation are not available on my system.
https://www.kernel.org/doc/Documentation/cgroup-v2.txt
It seems like I still have cgroup v1.
/sys/fs/cgroup/memory# ls
cgroup.clone_children memory.kmem.failcnt memory.kmem.tcp.usage_in_bytes memory.memsw.usage_in_bytes memory.swappiness
cgroup.event_control memory.kmem.limit_in_bytes memory.kmem.usage_in_bytes memory.move_charge_at_immigrate memory.usage_in_bytes
cgroup.procs memory.kmem.max_usage_in_bytes memory.limit_in_bytes memory.numa_stat memory.use_hierarchy
cgroup.sane_behavior memory.kmem.slabinfo memory.max_usage_in_bytes memory.oom_control notify_on_release
docker memory.kmem.tcp.failcnt memory.memsw.failcnt memory.pressure_level release_agent
memory.failcnt memory.kmem.tcp.limit_in_bytes memory.memsw.limit_in_bytes memory.soft_limit_in_bytes tasks
memory.force_empty memory.kmem.tcp.max_usage_in_bytes memory.memsw.max_usage_in_bytes memory.stat
Follow-up questions
Thanks Brian for the help. Please let me know if I should be creating a new question but I think it might be helpful to other if I just ask my questions here.
1) I am unable to add cgroup controllers, following the command in the doc
>> echo "+cpu +memory -io" > cgroup.subtree_control
However, I got "echo: write error: Invalid argument". Am I missing a prerequisite to this step?
2) I ran a docker container but the docker daemon log complained about not able to find "/sys/fs/cgroup/cpuset/docker/cpuset.cpus". It seems like docker is still expecting cgroupv1. What is the best way to enable cgroupv2 support on my docker daemon?
docker -v
Docker version 17.09.1-ce, build aedabb7
linux cgroups
linux cgroups
edited Oct 10 '18 at 17:18
Rui F Ribeiro
41.8k1483142
41.8k1483142
asked Sep 26 '18 at 4:34
user3397467user3397467
83
83
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The easiest way is to attempt to mount the pseudo-filesystem. If you can mount it to a location, then you can attempt to manage processes with the interface:
mount -t cgroup2 none $MOUNT_POINT
I see that you cited the documentation above. One of the points you may be missing is that the paths still need to be created. There's no reason you must manage cgroup resources at any particular location. It's just convention.
For example, you could totally present procfs
at /usr/monkeys
... as long as the directory /usr/monkeys
exists:
$ sudo mkdir /usr/monkeys
$ sudo mount -t proc none /usr/monkeys
$ ls -l /usr/monkeys
...
...
-r--r--r--. 1 root root 0 Sep 25 19:00 uptime
-r--r--r--. 1 root root 0 Sep 25 23:17 version
-r--------. 1 root root 0 Sep 25 23:17 vmallocinfo
-r--r--r--. 1 root root 0 Sep 25 18:57 vmstat
-r--r--r--. 1 root root 0 Sep 25 23:17 zoneinfo
$ sudo umount /usr/monkeys
In the same way I can do this with the cgroup v2 pseudo-filesystem:
$ sudo mount -t cgroup2 none /usr/monkeys
$ ls -l /usr/monkeys
total 0
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.controllers
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.depth
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.descendants
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.procs
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.stat
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.subtree_control
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.threads
drwxr-xr-x. 2 root root 0 Sep 23 16:58 init.scope
drwxr-xr-x. 2 root root 0 Sep 23 16:58 machine.slice
drwxr-xr-x. 59 root root 0 Sep 23 16:58 system.slice
drwxr-xr-x. 4 root root 0 Sep 23 16:58 user.slice
$ sudo umount /usr/monkeys
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
add a comment |
You could run the following command:
cat /proc/filesystems | grep cgroup
If your system supports cgroupv2, you would see:
nodev cgroup
nodev cgroup2
On a system with only cgroupv1, you would only see:
nodev cgroup
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471476%2fhow-do-i-check-cgroup-v2-is-installed-on-my-machine%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The easiest way is to attempt to mount the pseudo-filesystem. If you can mount it to a location, then you can attempt to manage processes with the interface:
mount -t cgroup2 none $MOUNT_POINT
I see that you cited the documentation above. One of the points you may be missing is that the paths still need to be created. There's no reason you must manage cgroup resources at any particular location. It's just convention.
For example, you could totally present procfs
at /usr/monkeys
... as long as the directory /usr/monkeys
exists:
$ sudo mkdir /usr/monkeys
$ sudo mount -t proc none /usr/monkeys
$ ls -l /usr/monkeys
...
...
-r--r--r--. 1 root root 0 Sep 25 19:00 uptime
-r--r--r--. 1 root root 0 Sep 25 23:17 version
-r--------. 1 root root 0 Sep 25 23:17 vmallocinfo
-r--r--r--. 1 root root 0 Sep 25 18:57 vmstat
-r--r--r--. 1 root root 0 Sep 25 23:17 zoneinfo
$ sudo umount /usr/monkeys
In the same way I can do this with the cgroup v2 pseudo-filesystem:
$ sudo mount -t cgroup2 none /usr/monkeys
$ ls -l /usr/monkeys
total 0
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.controllers
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.depth
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.descendants
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.procs
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.stat
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.subtree_control
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.threads
drwxr-xr-x. 2 root root 0 Sep 23 16:58 init.scope
drwxr-xr-x. 2 root root 0 Sep 23 16:58 machine.slice
drwxr-xr-x. 59 root root 0 Sep 23 16:58 system.slice
drwxr-xr-x. 4 root root 0 Sep 23 16:58 user.slice
$ sudo umount /usr/monkeys
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
add a comment |
The easiest way is to attempt to mount the pseudo-filesystem. If you can mount it to a location, then you can attempt to manage processes with the interface:
mount -t cgroup2 none $MOUNT_POINT
I see that you cited the documentation above. One of the points you may be missing is that the paths still need to be created. There's no reason you must manage cgroup resources at any particular location. It's just convention.
For example, you could totally present procfs
at /usr/monkeys
... as long as the directory /usr/monkeys
exists:
$ sudo mkdir /usr/monkeys
$ sudo mount -t proc none /usr/monkeys
$ ls -l /usr/monkeys
...
...
-r--r--r--. 1 root root 0 Sep 25 19:00 uptime
-r--r--r--. 1 root root 0 Sep 25 23:17 version
-r--------. 1 root root 0 Sep 25 23:17 vmallocinfo
-r--r--r--. 1 root root 0 Sep 25 18:57 vmstat
-r--r--r--. 1 root root 0 Sep 25 23:17 zoneinfo
$ sudo umount /usr/monkeys
In the same way I can do this with the cgroup v2 pseudo-filesystem:
$ sudo mount -t cgroup2 none /usr/monkeys
$ ls -l /usr/monkeys
total 0
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.controllers
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.depth
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.descendants
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.procs
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.stat
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.subtree_control
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.threads
drwxr-xr-x. 2 root root 0 Sep 23 16:58 init.scope
drwxr-xr-x. 2 root root 0 Sep 23 16:58 machine.slice
drwxr-xr-x. 59 root root 0 Sep 23 16:58 system.slice
drwxr-xr-x. 4 root root 0 Sep 23 16:58 user.slice
$ sudo umount /usr/monkeys
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
add a comment |
The easiest way is to attempt to mount the pseudo-filesystem. If you can mount it to a location, then you can attempt to manage processes with the interface:
mount -t cgroup2 none $MOUNT_POINT
I see that you cited the documentation above. One of the points you may be missing is that the paths still need to be created. There's no reason you must manage cgroup resources at any particular location. It's just convention.
For example, you could totally present procfs
at /usr/monkeys
... as long as the directory /usr/monkeys
exists:
$ sudo mkdir /usr/monkeys
$ sudo mount -t proc none /usr/monkeys
$ ls -l /usr/monkeys
...
...
-r--r--r--. 1 root root 0 Sep 25 19:00 uptime
-r--r--r--. 1 root root 0 Sep 25 23:17 version
-r--------. 1 root root 0 Sep 25 23:17 vmallocinfo
-r--r--r--. 1 root root 0 Sep 25 18:57 vmstat
-r--r--r--. 1 root root 0 Sep 25 23:17 zoneinfo
$ sudo umount /usr/monkeys
In the same way I can do this with the cgroup v2 pseudo-filesystem:
$ sudo mount -t cgroup2 none /usr/monkeys
$ ls -l /usr/monkeys
total 0
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.controllers
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.depth
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.descendants
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.procs
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.stat
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.subtree_control
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.threads
drwxr-xr-x. 2 root root 0 Sep 23 16:58 init.scope
drwxr-xr-x. 2 root root 0 Sep 23 16:58 machine.slice
drwxr-xr-x. 59 root root 0 Sep 23 16:58 system.slice
drwxr-xr-x. 4 root root 0 Sep 23 16:58 user.slice
$ sudo umount /usr/monkeys
The easiest way is to attempt to mount the pseudo-filesystem. If you can mount it to a location, then you can attempt to manage processes with the interface:
mount -t cgroup2 none $MOUNT_POINT
I see that you cited the documentation above. One of the points you may be missing is that the paths still need to be created. There's no reason you must manage cgroup resources at any particular location. It's just convention.
For example, you could totally present procfs
at /usr/monkeys
... as long as the directory /usr/monkeys
exists:
$ sudo mkdir /usr/monkeys
$ sudo mount -t proc none /usr/monkeys
$ ls -l /usr/monkeys
...
...
-r--r--r--. 1 root root 0 Sep 25 19:00 uptime
-r--r--r--. 1 root root 0 Sep 25 23:17 version
-r--------. 1 root root 0 Sep 25 23:17 vmallocinfo
-r--r--r--. 1 root root 0 Sep 25 18:57 vmstat
-r--r--r--. 1 root root 0 Sep 25 23:17 zoneinfo
$ sudo umount /usr/monkeys
In the same way I can do this with the cgroup v2 pseudo-filesystem:
$ sudo mount -t cgroup2 none /usr/monkeys
$ ls -l /usr/monkeys
total 0
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.controllers
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.depth
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.max.descendants
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.procs
-r--r--r--. 1 root root 0 Sep 23 16:58 cgroup.stat
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.subtree_control
-rw-r--r--. 1 root root 0 Sep 23 16:58 cgroup.threads
drwxr-xr-x. 2 root root 0 Sep 23 16:58 init.scope
drwxr-xr-x. 2 root root 0 Sep 23 16:58 machine.slice
drwxr-xr-x. 59 root root 0 Sep 23 16:58 system.slice
drwxr-xr-x. 4 root root 0 Sep 23 16:58 user.slice
$ sudo umount /usr/monkeys
answered Sep 26 '18 at 6:22
Brian RedbeardBrian Redbeard
1,691930
1,691930
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
add a comment |
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
Hi Brian, thanks for the help. Wondering if you could help me with my two follow up questions. Feel free to let me know if I should be creating a new question instead.
– user3397467
Sep 26 '18 at 13:43
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
@user3397467 You would be better off creating a separate question of the form "How do I configure Docker to use cgroupsv2?", calling out your how you're installing docker (via a distro shipped package, docker CE from their repos, etc), the distro you are running, and any configurations you may have set up to that point.
– Brian Redbeard
Sep 26 '18 at 16:10
add a comment |
You could run the following command:
cat /proc/filesystems | grep cgroup
If your system supports cgroupv2, you would see:
nodev cgroup
nodev cgroup2
On a system with only cgroupv1, you would only see:
nodev cgroup
add a comment |
You could run the following command:
cat /proc/filesystems | grep cgroup
If your system supports cgroupv2, you would see:
nodev cgroup
nodev cgroup2
On a system with only cgroupv1, you would only see:
nodev cgroup
add a comment |
You could run the following command:
cat /proc/filesystems | grep cgroup
If your system supports cgroupv2, you would see:
nodev cgroup
nodev cgroup2
On a system with only cgroupv1, you would only see:
nodev cgroup
You could run the following command:
cat /proc/filesystems | grep cgroup
If your system supports cgroupv2, you would see:
nodev cgroup
nodev cgroup2
On a system with only cgroupv1, you would only see:
nodev cgroup
answered yesterday
Wadih M.Wadih M.
516213
516213
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471476%2fhow-do-i-check-cgroup-v2-is-installed-on-my-machine%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
-cgroups, linux