From: 666Goofy666 <666goofy666@proton.me>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: 666Goofy666 <666goofy666@proton.me>
Subject: [PATCH docs 3/6] pct: cgroups: fix systemd supported version
Date: Sun, 08 Nov 2026 21:35:21 +0000 [thread overview]
Message-ID: <20261108213430.139213-4-666goofy666@proton.me> (raw)
In-Reply-To: <20261108213430.139213-1-666goofy666@proton.me>
From: 666Goofy666 <666goofy666@proton.me>
Although systemd introduced cgroup v2 support in version 230, code
(unified_cgroupv2_support) requires 232 or newer to ensure broader
controller support.
Signed-off-by: 666Goofy666 <666goofy666@proton.me>
---
pct.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pct.adoc b/pct.adoc
index ed99e8b..48cf56e 100644
--- a/pct.adoc
+++ b/pct.adoc
@@ -725,7 +725,7 @@ completely different way. Because of this, file system quotas are currently not
supported in a pure 'cgroupv2' environment.
'cgroupv2' support by the container's OS is needed to run in a pure 'cgroupv2'
-environment. Containers running 'systemd' version 231 or newer support
+environment. Containers running 'systemd' version 232 or newer support
'cgroupv2' footnote:[this includes all newest major versions of container
templates shipped by {pve}], as do containers not using 'systemd' as init
system footnote:[for example Alpine Linux].
--
2.56.0
next prev parent reply other threads:[~2026-11-08 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 21:35 [PATCH docs 0/6] container documentation updates 666Goofy666
2026-11-08 21:35 ` [PATCH docs 1/6] fix #7852: pct: network: fix max number interfaces 666Goofy666
2026-11-08 21:35 ` [PATCH docs 2/6] pct: snapshots: fix example variable 666Goofy666
2026-11-08 21:35 ` 666Goofy666 [this message]
2026-11-08 21:35 ` [PATCH docs 4/6] pct: configuration: update configuration keys 666Goofy666
2026-11-08 21:35 ` [PATCH docs 5/6] pct: memory: change to cgroup v2 666Goofy666
2026-11-08 21:35 ` [PATCH docs 6/6] pct: mountpoints: fix mount point typo 666Goofy666
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261108213430.139213-4-666goofy666@proton.me \
--to=666goofy666@proton.me \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox