From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Filip Schauer <f.schauer@proxmox.com>
Subject: Re: [pve-devel] [PATCH container] config: clarify description of host-managed netdev option
Date: Fri, 23 Jan 2026 16:16:57 +0100 [thread overview]
Message-ID: <de14d188-6db3-4174-9024-b07d8302ce65@proxmox.com> (raw)
In-Reply-To: <20251124113358.43730-1-f.schauer@proxmox.com>
Am 24.11.25 um 12:34 schrieb Filip Schauer:
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
> ---
> src/PVE/LXC/Config.pm | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
> index 6be38a2..6445528 100644
> --- a/src/PVE/LXC/Config.pm
> +++ b/src/PVE/LXC/Config.pm
> @@ -915,7 +915,11 @@ our $netconf_desc = {
> 'host-managed' => {
> type => 'boolean',
> description =>
> - "Whether this interface's IP configuration should be managed by the host.",
> + "Whether this interface's IP configuration should be managed by the host. When enabled,"
> + . " the host (rather than the container) is responsible for the interface's IP"
> + . " configuration. The container should not run its own DHCP client or network manager"
> + . " on this interface. This is useful for containers that lack an internal network"
> + . " management stack, like many application containers.",
Great to have more context, but we have "verbose_description" schema property,
to avoid crowding places where short description is a better fit. This instance
here is a bit borderline, so mostly to put the availability of that property on
your (and others) radar.
> optional => 1,
> },
> };
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-23 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 11:33 Filip Schauer
2026-01-14 13:04 ` [pve-devel] applied: " Fiona Ebner
2026-01-23 15:16 ` Thomas Lamprecht [this message]
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=de14d188-6db3-4174-9024-b07d8302ce65@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.schauer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox