From f64344d1da32ab3760c87e435c84735c7c8b1e4c Mon Sep 17 00:00:00 2001 From: rcourtman Date: Sat, 15 Nov 2025 09:56:27 +0000 Subject: [PATCH] Add Proxmox LXC instructions to bootstrap token screen When Pulse runs in Docker inside a Proxmox LXC container, users need specific instructions to retrieve the bootstrap token. Added pct exec and pct enter commands to the Docker instructions section. Now shows three scenarios: 1. Direct Docker host: docker exec 2. Kubernetes: kubectl exec 3. Proxmox LXC with Docker: pct exec / pct enter This makes first-time setup easier for users deploying Pulse in LXC containers on Proxmox. --- frontend-modern/src/components/FirstRunSetup.tsx | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/frontend-modern/src/components/FirstRunSetup.tsx b/frontend-modern/src/components/FirstRunSetup.tsx index 665b374..7ad0e67 100644 --- a/frontend-modern/src/components/FirstRunSetup.tsx +++ b/frontend-modern/src/components/FirstRunSetup.tsx @@ -319,18 +319,22 @@ IMPORTANT: Keep these credentials secure! >
-
# From container host:
+
# From Docker host:
docker exec <container-name> cat {bootstrapTokenPath()} -
# Or kubectl for Kubernetes:
+
# For Kubernetes:
kubectl exec <pod-name> -- cat {bootstrapTokenPath()} -
# Or exec into the container:
+
# For Proxmox LXC running Docker:
+ pct exec <ctid> -- docker exec <container-name> cat {bootstrapTokenPath()} +
# Or enter the LXC container first:
+ pct enter <ctid> +
# Then inside LXC:
# For Proxmox LXC, run from Proxmox host:
pct enter <ctid>
# Or directly retrieve:
pct exec <ctid> -- cat {bootstrapTokenPath()} -
# Or from inside the container:
+
# Or from inside the LXC container:
cat {bootstrapTokenPath()}