[GH-ISSUE #4798] Netbird install script doesn't take into account rpm-ostree requiring a reboot to layer packages #9361

Open
opened 2026-08-05 01:21:50 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @sftp65535 on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4798

Describe the problem

On systems like Fedora Silverblue, rpm-ostree "installs" (layers) new packages on reboot. By default, the install script will try to start the service without knowing that netbird hasn't been layered yet, subsequently failing on these two lines:

ensure the service is started after install
${SUDO} netbird service install || true
${SUDO} netbird service start || true

curl -fsSL https://pkgs.netbird.io/install.sh | sh
[...]
Staging deployment... done
Added:
  netbird-0.59.13-1.x86_64
Changes queued for next boot. Run "systemctl reboot" to start a reboot
sudo: netbird: command not found
sudo: netbird: command not found
Installation has been finished. To connect, you need to run NetBird by executing the following command:

netbird up

To Reproduce

Run the Netbird install script on a system using rpm-ostree as package manager.

Expected behavior

A small warning should be displayed after installation, advising the user to either enable the service manually upon rebooting the machine or running the script again to start the Netbird service.

Personally I enabled it with sudo systemctl enable --now netbird.service, which seems like a simpler approach, and integrates better with distributions using systemd. Maybe it's worth considering switching to systemd entirely given that it's one step less, but I am not privy to the inner workings of every Linux distro.

NetBird version

0.59.13

Originally created by @sftp65535 on GitHub (Nov 16, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4798 **Describe the problem** On systems like Fedora Silverblue, rpm-ostree "installs" (layers) new packages on reboot. By default, the install script will try to start the service without knowing that netbird hasn't been layered yet, subsequently failing on these two lines: > ensure the service is started after install > ${SUDO} netbird service install || true > ${SUDO} netbird service start || true ``` curl -fsSL https://pkgs.netbird.io/install.sh | sh [...] Staging deployment... done Added: netbird-0.59.13-1.x86_64 Changes queued for next boot. Run "systemctl reboot" to start a reboot sudo: netbird: command not found sudo: netbird: command not found Installation has been finished. To connect, you need to run NetBird by executing the following command: netbird up ``` **To Reproduce** Run the Netbird install script on a system using rpm-ostree as package manager. **Expected behavior** A small warning should be displayed after installation, advising the user to either enable the service manually upon rebooting the machine or running the script again to start the Netbird service. Personally I enabled it with `sudo systemctl enable --now netbird.service`, which seems like a simpler approach, and integrates better with distributions using systemd. Maybe it's worth considering switching to systemd entirely given that it's one step less, but I am not privy to the inner workings of every Linux distro. **NetBird version** `0.59.13`
saavagebueno added the triage-needed label 2026-08-05 01:21:50 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#9361