Hello I'm trying to setup sparkbox on a proxmox server with a container running ubuntu. I'm able to get the install going and when it finishes it gave me the link but no bootstrap token to paste into it. I tried sparkbox help to see if there was something I was missing. After looking around I ran sparkbox install which seemed to boot up the install wizard which hadnt shown up before. I went through it filling everything out and when it was done it downloaded all the container images and then was just done with no bootstrap token. Where did I go wrong. Am I missing something about running this in a proxmox container? This is my first server so odds are I've missed a good amount.
13 replies
AvantMagus wrote:
As someone who has gone down this route, I suggest you use a vm rather than a container. Also install everything as root inside the vm rather than a privileged user.
tomspark wrote:
Love to hear it — welcome aboard! Zero errors on a fresh dashboard is exactly where you want to be. And yeah, a VM tends to be a smoother ride than a container for this, so that was a good call. Have fun getting things set up — if anything acts weird as you switch on more apps, just post and we'll help you sort it.
AvantMagus wrote:
Good deal! I learned the hard way that containers struggle with Docker. VM's work way better for the nested virtualization.
Ihavenoidea wrote:
https://demox.world/post/no-bootstrap-token-12322 the steps in this post helped me
popuman wrote:
From the man himself: Type sudo sparkbox bootstrap-token and it will generate a new one. Copy what it prints and paste into the dashboard's first-run claim screen.
tomspark wrote:
You didn't do anything wrong here. Sometimes the token just doesn't print at the very end of the install, and there's a one-line fix. The folks above nailed it: on your server, run sudo sparkbox bootstrap-token, copy the whole line it prints out, and paste that into the claim box on the dashboard page you already opened. That'll get you in. And honestly, nice work getting this far on your first server, doing it inside a Proxmox container is the harder route, so you're doing great.
Technofly17 wrote:
So I've run the sudo sparkbox bootstrap-token and nothing shows up. Do I need to look somewhere else for the token?
tomspark wrote:
No worries, you're closer than it looks. When that command prints nothing back, it usually means the token was already used once, which is actually fine: it means the dashboard is past the token step and just wants a normal login now. Two things would help me. First, on the dashboard page, are you seeing a box asking for a token, or a regular username and password login? Second, run this to set yourself a fresh admin password: sudo sparkbox reset-password Log in with whatever it prints out. Tell me which box you saw and we'll get you in.
Technofly17 wrote:
Oh that worked like a charm I just inputed the new password with no bootstrap token and it fired right up. It seems like portainer and some other containers are unhealthy though and keep repeatedly crashing. I might just scrap this container and do a fresh download of sparkbox in a new one now that I think I understand it a bit more.
tomspark wrote:
AvantMagus makes a fair point — a VM is the smoother path long-term if you ever want to start fresh. But you likely don't need to rebuild anything right now. Technofly17, did the reset-password command get you logged in? If you're in, you're good as-is; if not, tell me what the dashboard screen shows and we'll finish it from here.
Technofly17 wrote:
Duly noted I've restarted the sparkbox journey with a VM now which has been a journey all on its own. Seems to be going pretty smoothly so far!
Technofly17 wrote:
Thanks everyone for the help! I now have sparkbox dashboard up and running with zero errors I am very excited to start self hosting with all these available apps! The Vm was way smoother than the container for setup.
tomspark wrote:
Appreciate you jumping in to help here — that's exactly what makes this community great. And you nailed it: a VM sidesteps the nested-virtualization headaches that bite people running this in a container. Thanks AvantMagus.