From: Lucas Barros <lucasbarros.kam@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs] fix #7852: pct: network: document limit of 32 interfaces
Date: Sat, 7 Nov 2026 19:28:02 -0300 [thread overview]
Message-ID: <20261107222802.20526-1-lucasbarros.kam@gmail.com> (raw)
The maximum number of network interfaces of a container was raised from
10 to 32 in pve-container and the web UI, but the documentation still
mentions the old limit and only lists the options up to 'net9'.
Update the number and the option range, and fix the grammar of the
sentence introducing the list of settings while at it.
Signed-off-by: Lucas Barros <lucasbarros.kam@gmail.com>
---
The limit was raised by pve-container commit 6dd2d4c ("Bump maximum
number of container net interfaces from 10 to 32") and pve-manager
commit e08f07de. Also checked the other limits in the chapter: the
256 mount points (mp0 to mp255) still match $MAX_MOUNT_POINTS.
I did not build the docs locally (no asciidoc toolchain here), the
change only touches plain text. All lines stay within 80 columns.
This patch was prepared with the help of an LLM based coding assistant; I
reviewed the change and ran the tests mentioned above myself.
pct.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pct.adoc b/pct.adoc
index cd3130f..25dc1fe 100644
--- a/pct.adoc
+++ b/pct.adoc
@@ -593,9 +593,9 @@ Network
[thumbnail="screenshot/gui-create-ct-network.png"]
-You can configure up to 10 network interfaces for a single container.
-The corresponding options are called `net0` to `net9`, and they can contain the
-following setting:
+You can configure up to 32 network interfaces for a single container.
+The corresponding options are called `net0` to `net31`, and they can contain the
+following settings:
include::generated/pct-network-opts.adoc[]
--
2.50.1 (Apple Git-155)
reply other threads:[~2026-11-07 22:28 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=20261107222802.20526-1-lucasbarros.kam@gmail.com \
--to=lucasbarros.kam@gmail.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.