From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES container 0/3] add missing no-op methods for unmanaged CTs
Date: Wed, 4 Feb 2026 10:17:31 +0100 [thread overview]
Message-ID: <20260204091740.102914-1-d.kral@proxmox.com> (raw)
Small fixes, which add missing no-op methods for unmanaged containers,
where the first fixes unmanaged containers to start again and be able to
create/clone unmanaged containers, while the latter is only removing an
error message.
Tested with an unmanaged voidlinux container.
Daniel Kral (3):
setup: add no-op check_systemd_nesting for unmanaged CTs
setup: add no-op detect_architecture for unmanaged CTs
setup: make the architecture fall back to amd64 for empty strings
src/PVE/LXC/Setup.pm | 2 +-
src/PVE/LXC/Setup/Unmanaged.pm | 13 ++++++++++++-
2 files changed, 13 insertions(+), 2 deletions(-)
--
2.47.3
next reply other threads:[~2026-02-04 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 9:17 Daniel Kral [this message]
2026-02-04 9:17 ` [PATCH container 1/3] setup: add no-op check_systemd_nesting " Daniel Kral
2026-02-04 9:35 ` Daniel Kral
2026-02-04 9:17 ` [PATCH container 2/3] setup: add no-op detect_architecture " Daniel Kral
2026-02-04 9:17 ` [PATCH container 3/3] setup: make the architecture fall back to amd64 for empty strings Daniel Kral
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=20260204091740.102914-1-d.kral@proxmox.com \
--to=d.kral@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.