From 14ac4bbb8b9245037c26d21e93e84b3f1c43b26d Mon Sep 17 00:00:00 2001 From: rcourtman Date: Mon, 10 Nov 2025 12:20:41 +0000 Subject: [PATCH] Add Proxmox LXC instructions to bootstrap token UI Users were confused about how to access the bootstrap token in Proxmox LXC containers. They were trying to use the Proxmox web console instead of 'pct enter' from the Proxmox host. This adds explicit instructions in the FirstRunSetup UI that show: - pct enter for interactive access - pct exec -- cat /etc/pulse/.bootstrap_token for direct retrieval - Clear indication that commands should be run from Proxmox host The instructions only display when the deployment is not Docker and the bootstrap token path is /etc/pulse/.bootstrap_token (indicating LXC). Fixes #681 --- frontend-modern/src/components/FirstRunSetup.tsx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/frontend-modern/src/components/FirstRunSetup.tsx b/frontend-modern/src/components/FirstRunSetup.tsx index f93dd85..34c771e 100644 --- a/frontend-modern/src/components/FirstRunSetup.tsx +++ b/frontend-modern/src/components/FirstRunSetup.tsx @@ -326,6 +326,13 @@ IMPORTANT: Keep these credentials secure! kubectl exec <pod-name> -- cat {bootstrapTokenPath()}
# Or exec into the container:
+ +
# For Proxmox LXC, run from Proxmox host:
+ pct enter <ctid> +
# Or directly retrieve:
+ pct exec <ctid> -- cat {bootstrapTokenPath()} +
# Or from inside the container:
+
cat {bootstrapTokenPath()}