danvics/Pulse
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add Proxmox LXC instructions to bootstrap token UI

Browse source 
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 <ctid> for interactive access
- pct exec <ctid> -- 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
This commit is contained in:
rcourtman 2025-11-10 12:20:41 +00:00
parent 9fcf0b35e8
commit 14ac4bbb8b
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
frontend-modern/src/components/FirstRunSetup.tsx
View file

@ -326,6 +326,13 @@ IMPORTANT: Keep these credentials secure!
kubectl exec &lt;pod-name&gt; -- cat {bootstrapTokenPath()}
<div class="text-gray-500 dark:text-gray-400 mt-2 mb-1"># Or exec into the container:</div>
</Show>
<Show when={!isDocker() && bootstrapTokenPath() === '/etc/pulse/.bootstrap_token'}>
<div class="text-blue-600 dark:text-blue-400 mb-1"># For Proxmox LXC, run from Proxmox host:</div>
pct enter &lt;ctid&gt;
<div class="text-gray-500 dark:text-gray-400 mt-2 mb-1"># Or directly retrieve:</div>
pct exec &lt;ctid&gt; -- cat {bootstrapTokenPath()}
<div class="text-gray-500 dark:text-gray-400 mt-2 mb-1"># Or from inside the container:</div>
</Show>
cat {bootstrapTokenPath()}
</div>
</Show>