From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2] pct: clarify needed systemd-versions for cgroupv2 support
Date: Thu, 1 Jul 2021 13:04:34 +0200 [thread overview]
Message-ID: <20210701110434.1151631-1-s.ivanov@proxmox.com> (raw)
versions determined through systemd's changelog, and a few empiric
tests.
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
changes v1->v2:
* fixed the wrong ubuntu-version in the note (I tested 16.04 LTS not 16.10)
Huge thanks to Thomas for catching this!!
pct.adoc | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/pct.adoc b/pct.adoc
index b03b6ba..9c512df 100644
--- a/pct.adoc
+++ b/pct.adoc
@@ -518,8 +518,17 @@ Another important difference is that the 'devices' controller is configured in a
completely different way. Because of this, file system quotas are currently not
supported in a pure 'cgroupv2' environment.
-If file system quotas are not required and the containers are new enough to
-understand 'cgroupv2', it is recommended to stick to the new default.
+'cgroupv2' support by the container's OS is needed to run in a pure 'cgroupv2'
+environment. Containers running 'systemd' version 231 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].
+
+NOTE: CentOS 7 and Ubuntu 16.04 are two prominent Linux distributions, which
+have a 'systemd' version that is too old to run in a 'cgroupv2' environment.
+
+If file system quotas are not required and the containers support 'cgroupv2',
+it is recommended to stick to the new default.
To switch back to the previous version the following kernel command line
parameter can be used:
--
2.30.2
reply other threads:[~2021-07-01 11:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210701110434.1151631-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.