[pve-devel] [PATCH container] config: clarify description of entrypoint property

[Filip Schauer <f.schauer@proxmox.com>]

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