From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container] config: clarify description of entrypoint property
Date: Tue, 18 Nov 2025 12:24:26 +0100 [thread overview]
Message-ID: <20251118112556.51942-1-f.schauer@proxmox.com> (raw)
The previous description implied that `entrypoint` must be an absolute
path to a binary within the container's rootfs. In reality, the
entrypoint may be any command, optionally with arguments. It can start
with an absolute path, a path relative to the container's working
directory, or the name of a binary found in the containers PATH
environment.
Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
src/PVE/LXC/Config.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
index 8595a8b..af2693c 100644
--- a/src/PVE/LXC/Config.pm
+++ b/src/PVE/LXC/Config.pm
@@ -641,7 +641,8 @@ my $confdesc = {
entrypoint => {
optional => 1,
type => 'string',
- description => "Absolute path from container rootfs to the binary to use as init.",
+ description => "Command to run as init, optionally with arguments;"
+ . " may start with an absolute path, relative path, or a binary in \$PATH.",
pattern => qr/[^\x00-\x1F\x7F]+/,
default => '/sbin/init',
},
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-11-18 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 11:24 Filip Schauer [this message]
2025-11-18 12:19 ` [pve-devel] applied: " Thomas Lamprecht
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=20251118112556.51942-1-f.schauer@proxmox.com \
--to=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