From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container v2 1/4] setup: plugin: add missing check_systemd_nesting stub
Date: Fri, 6 Feb 2026 13:45:02 +0100 [thread overview]
Message-ID: <20260206124513.310674-2-d.kral@proxmox.com> (raw)
In-Reply-To: <20260206124513.310674-1-d.kral@proxmox.com>
Suggested-by: Robert Obkircher <r.obkircher@proxmox.com>
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
changes from v1:
- new!
src/PVE/LXC/Setup/Plugin.pm | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/PVE/LXC/Setup/Plugin.pm b/src/PVE/LXC/Setup/Plugin.pm
index fbcfa8e..cb8e5c4 100644
--- a/src/PVE/LXC/Setup/Plugin.pm
+++ b/src/PVE/LXC/Setup/Plugin.pm
@@ -57,6 +57,11 @@ sub get_ct_init_path {
croak "implement me in sub-class\n";
}
+sub check_systemd_nesting {
+ my ($self) = @_;
+ croak "implement me in sub-class\n";
+}
+
sub ssh_host_key_types_to_generate {
my ($self) = @_;
croak "implement me in sub-class\n";
--
2.47.3
next prev parent reply other threads:[~2026-02-06 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 12:45 [PATCH-SERIES container v2 0/4] add missing no-op methods for unmanaged CTs Daniel Kral
2026-02-06 12:45 ` Daniel Kral [this message]
2026-02-06 12:45 ` [PATCH container v2 2/4] fix #7270: setup: add no-op check_systemd_nesting " Daniel Kral
2026-02-06 12:45 ` [PATCH container v2 3/4] setup: add no-op detect_architecture " Daniel Kral
2026-02-06 13:09 ` Fiona Ebner
2026-02-06 14:30 ` Thomas Lamprecht
2026-02-06 15:04 ` Fiona Ebner
2026-02-06 14:30 ` applied: " Thomas Lamprecht
2026-02-06 12:45 ` [PATCH container v2 4/4] setup: make the architecture fall back to amd64 for falsy values Daniel Kral
2026-02-06 14:30 ` applied: " Thomas Lamprecht
2026-02-06 13:18 ` partially-applied: [PATCH-SERIES container v2 0/4] add missing no-op methods for unmanaged CTs Fiona Ebner
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=20260206124513.310674-2-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.