From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Robert Obkircher <r.obkircher@proxmox.com>
Subject: [pve-devel] applied: [PATCH v6 pve-container 0/5] warn that nesting may be required
Date: Wed, 14 Jan 2026 12:55:00 +0100 [thread overview]
Message-ID: <176839155287.195333.1843250873801791647.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251119142738.26840-1-r.obkircher@proxmox.com>
On Wed, 19 Nov 2025 15:24:52 +0100, Robert Obkircher wrote:
> This patch adds a task-log warning on CT start if systemd is detected.
>
> Changes since v5:
> - improved comment
> - (attempted to rewrite path concatenation but ended up leaving it
> unchanged)
>
> [...]
Applied, series thanks! Dropped the 'fix #6897' prefix from 4/5,
because it's not directly related to the bug. Made a small style fix
in patch 3/5 dropping parentheses for post-if and made the commit
title for 5/5 more specific.
[1/5] Ensure that container startup warnings are displayed if startup fails.
commit: 575426fa35b6eb299c412880ae8a550fa1ff4327
[2/5] Propagate prestart-hook warnings to task-log.
commit: a5213c06b121ae0e045a3582001087f966200e70
[3/5] fix #6897: warn that nesting may be required for systemd
commit: 46f7fb0f5408c6919d62b3cd8a2f6850077e9f48
[4/5] setup: constrain and untaint path for systemd version detection
commit: c30fb192bbb8a5f12ce8003021541b5ae404e668
[5/5] fix #6897: also warn that nesting may be required for systemd in the post_clone and post_create hooks
commit: c4e1e249e310a9c55f7baee630d93c816913b740
_______________________________________________
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-14 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 14:24 [pve-devel] " Robert Obkircher
2025-11-19 14:24 ` [pve-devel] [PATCH v6 pve-container 1/5] Ensure that container startup warnings are displayed if startup fails Robert Obkircher
2025-11-19 14:24 ` [pve-devel] [PATCH v6 pve-container 2/5] Propagate prestart-hook warnings to task-log Robert Obkircher
2025-11-19 14:24 ` [pve-devel] [PATCH v6 pve-container 3/5] fix #6897: warn that nesting may be required for systemd Robert Obkircher
2025-11-19 14:24 ` [pve-devel] [PATCH v6 pve-container 4/5] fix #6897: constrain and untaint path for systemd version detection Robert Obkircher
2025-11-19 14:24 ` [pve-devel] [PATCH v6 pve-container 5/5] fix #6897: also warn in the post_clone and post_create hooks Robert Obkircher
2026-01-14 11:55 ` Fiona Ebner [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=176839155287.195333.1843250873801791647.b4-ty@proxmox.com \
--to=f.ebner@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