all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH container] config: clarify description of entrypoint property
@ 2025-11-18 11:24 Filip Schauer
  2025-11-18 12:19 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Filip Schauer @ 2025-11-18 11:24 UTC (permalink / raw)
  To: pve-devel

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH container] config: clarify description of entrypoint property
  2025-11-18 11:24 [pve-devel] [PATCH container] config: clarify description of entrypoint property Filip Schauer
@ 2025-11-18 12:19 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2025-11-18 12:19 UTC (permalink / raw)
  To: pve-devel, Filip Schauer

On Tue, 18 Nov 2025 12:24:26 +0100, Filip Schauer wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/1] config: clarify description of entrypoint property
      commit: 72e99d735d9b7447d667422904d3eb40e1f88a36


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-11-18 12:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-11-18 11:24 [pve-devel] [PATCH container] config: clarify description of entrypoint property Filip Schauer
2025-11-18 12:19 ` [pve-devel] applied: " Thomas Lamprecht

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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal