Differentiate running netbird as root user and with sudo commands

This commit is contained in:
Theodor S. Midtlien
2026-10-22 17:14:15 +02:00
parent 136fad7e3d
commit 2354b4307d
3 changed files with 4 additions and 4 deletions
+2 -2
View File
@@ -78,7 +78,7 @@ sudo netbird up --setup-key <YOUR_SETUP_KEY>
<Note> <Note>
On a machine with no console, such as a server, run `netbird up` with `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine). On a machine with no console, such as a server, run `netbird up` with `sudo`, or as root. If an administrator gave the default profile to a user with `netbird profile claim default --owner <user>`, run `netbird up` as that user without `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine).
</Note> </Note>
After running the second command, the terminal will confirm Connected. Your headless device is now part of your NetBird network. After running the second command, the terminal will confirm Connected. Your headless device is now part of your NetBird network.
@@ -155,7 +155,7 @@ sudo netbird up --setup-key <YOUR_SETUP_KEY>
<Note> <Note>
On a machine with no console, such as a server, run `netbird up` with `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine). On a machine with no console, such as a server, run `netbird up` with `sudo`, or as root. If an administrator gave the default profile to a user with `netbird profile claim default --owner <user>`, run `netbird up` as that user without `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine).
</Note> </Note>
After running the second command, the terminal will confirm Connected. Your headless device is now part of your NetBird network. After running the second command, the terminal will confirm Connected. Your headless device is now part of your NetBird network.
+1 -1
View File
@@ -498,7 +498,7 @@ Alternatively, if you are hosting your own Management Service provide `--managem
<Note> <Note>
On a machine with no console, such as a server, run `netbird up` with `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine). On a machine with no console, such as a server, run `netbird up` with `sudo`, or as root. If an administrator gave the default profile to a user with `netbird profile claim default --owner <user>`, run `netbird up` as that user without `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine).
</Note> </Note>
<Note> <Note>
@@ -16,7 +16,7 @@ sudo netbird up --setup-key <SETUP KEY>
<Note> <Note>
On a machine with no console, such as a server, run `netbird up` with `sudo`, or as root. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine). On a machine with no console, such as a server, run `netbird up` with `sudo`, or as root. If an administrator gave the default profile to a user with `netbird profile claim default --owner <user>`, run `netbird up` as that user without `sudo`. See [Set up a headless machine](/client/profile-ownership#set-up-a-headless-machine).
</Note> </Note>
You can also pre-populate the client configuration ahead of first start, so peers come up fully configured and register with no manual steps. See [Bootstrap peers via config file](/manage/peers/bootstrap-via-config-file). You can also pre-populate the client configuration ahead of first start, so peers come up fully configured and register with no manual steps. See [Bootstrap peers via config file](/manage/peers/bootstrap-via-config-file).