From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Robert Obkircher <r.obkircher@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager] fix #6897: ui: add hint that lxc nesting is usually required
Date: Mon, 13 Oct 2025 13:26:08 +0200 [thread overview]
Message-ID: <7248c2c7-2d29-4477-97ea-321c33313f95@proxmox.com> (raw)
In-Reply-To: <20251013100244.48133-1-r.obkircher@proxmox.com>
Am 13.10.25 um 12:03 schrieb Robert Obkircher:
> Modern distributions require nesting to access /sys and /proc.
> Someone ran into issues when trying to disable it and suggested
> adding a warning on the Web UI.
Thanks for your patch, the changes track besides maybe some wording
improvements, but not sure how much this really helps, as it probably
would only guard against unticking the "nesting" checkbox on CT
creation, but not be visible when one updates a existing old CT without
nesting from inside the CT to a newer distro release that then requires
nesting. I asked some follow-up questions to the reporter on BZ to try
to better understand what they meant and what would have helped them.
>
> Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=6897
> Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
> ---
> www/manager6/lxc/CreateWizard.js | 1 +
> www/manager6/lxc/FeaturesEdit.js | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/www/manager6/lxc/CreateWizard.js b/www/manager6/lxc/CreateWizard.js
> index 0f6fcce8..e8093c0a 100644
> --- a/www/manager6/lxc/CreateWizard.js
> +++ b/www/manager6/lxc/CreateWizard.js
> @@ -81,6 +81,7 @@ Ext.define('PVE.lxc.CreateWizard', {
> disabled: '{!unprivileged}',
> },
> fieldLabel: gettext('Nesting'),
> + boxLabel: gettext('required for many distributions'),
> },
> ],
> column2: [
> diff --git a/www/manager6/lxc/FeaturesEdit.js b/www/manager6/lxc/FeaturesEdit.js
> index 271f1cc3..df33e67c 100644
> --- a/www/manager6/lxc/FeaturesEdit.js
> +++ b/www/manager6/lxc/FeaturesEdit.js
> @@ -36,6 +36,7 @@ Ext.define('PVE.lxc.FeaturesInputPanel', {
> xtype: 'proxmoxcheckbox',
> fieldLabel: gettext('Nesting'),
> name: 'nesting',
> + boxLabel: gettext('required for many distributions'),
> },
> {
> xtype: 'proxmoxcheckbox',
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-13 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 10:02 Robert Obkircher
2025-10-13 11:26 ` 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=7248c2c7-2d29-4477-97ea-321c33313f95@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=r.obkircher@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