Pulse: bootstrap token

Support
,
1

Module: pulse

During the first start I need to discover the credentials

image
image1600×1042 81 KB

  1. to determine the docker name via runagent -m pulse1 podman ps → the name “puls-app” was obtained
  2. executing ~# runagent -m pulse1 exec pulse-app cat /data/.bootstrap_token
  3. result:
    Traceback (most recent call last):
    File “/usr/local/bin/runagent”, line 112, in
    os.execvp(args.COMMAND, [args.COMMAND] + args.ARGS)
    File “”, line 574, in execvp
    File “”, line 616, in _execvpe
    File “”, line 607, in _execvpe
    FileNotFoundError: [Errno 2] No such file or directory

What I did wrong?

Perhaps it would be useful to complete the documentation.

2

Sorry, I updated pulse recently and didn’t get that it needs that bootstrap token now. I updated the README.

runagent -m pulse1 podman exec pulse-app cat /data/.bootstrap_token
1 Like
3

hmm… :thinking:
Isn’t it what I did?
Nevertheless, I still received the error FileNotFoundError: [Errno 2] No such file or directory

4

The first “FIle not found” error was because you missed “podman” in your command.

After entering the token to create the admin user, the file /data/.bootstrap_token is deleted, therefore the second “file not found” error.

To start over:

runagent -m pulse1 systemctl --user stop pulse
runagent -m pulse1 podman volume rm -a
runagent -m pulse1 systemctl --user start pulse

Now the token should be shown again by entering:

runagent -m pulse1 podman exec pulse-app cat /data/.bootstrap_token

This bootstrap token is used only once to create the admin.

2 Likes
5

Thank you @mrmarkuz

You know the sayings..
“Ich sehe den Wald vor lauter Bäumen nicht” or “Ich habe Tomaten auf den Augen”
And somtimes you are “Mit Blindheit geschlagen”.

1 Like