Arch Linux User Repository

Hi @tarball, I'm from the NetBird team.

This socket path mismatch has been fixed upstream. The CLI, UI, and SSH client now auto-discover the daemon socket when the default /var/run/netbird.sock doesn't exist - they scan /var/run/netbird/*.sock and use it if exactly one is found. So netbird@main.service will work out of the box without needing --daemon-addr or NB_DAEMON_ADDR.

The fix is in https://github.com/netbirdio/netbird/commit/ef82905526a5944e9aac96e04b8b7ee67d27c9b9. It's included as of v0.66.

Sure, go ahead if you wish. I'll push an update when the deletion request is accepted.

go build will probably have to be moved inside package() even if it's not the canonical way of doing it; few users need -signal and -management subpackages already, and adding -ui will slow down the build process even more for them.

edit: or maybe not: yay, the most popular AUR helper, builds all subpackages anyway even when installing just one of them. I haven't tested other helpers yet.

FYI: we will make the NB_CONFIG/--config point to the location of the default profile soon, so it will be 100% compatible with pre-0.52.x

nazarewk,

Okay, the next version it is then. I'll use my own relay unit until netbird provides a replacement, or discontinues the relay daemon.

The idea for using templated units was never running several copies of netbird simultaneously (I understand it's not that simple), but to be able to easily switch between several configuration files (e.g. work & home). Since you've now solved it by other means, maybe it makes sense to remove the template altogether.

@tarball Actually with 0.52.0+ the client package does need to be adjusted due to:

• introduction of configuration profiles (they're put inside NB_STATE_DIR or /var/lib/netbird by default)

• we're currently migrating it only from /etc/netbird/config.json directly (ignoring the flag/envvar), I'll see what we can do about it,

• deprecating NB_CONFIG / --config flag

I usually ignore comments like this, but oh well.

This package has shipped systemd units since the beginning (June 2021, when the project was just started and was called "wiretrustee"). These units were written specifically for this package and were then upstreamed with minor changes in November 2023.

These are the OG files, and this configuration/variable names have been used since before upstream had any units at all. I can't just break existing users' configurations for no reason.

netbird-bin has recently been migrated to upstream units, but I can't do this one yet because there's no upstream replacement for the relay service, and they currently refuse to accept one.

This package will be migrated:

1. when they change their mind;
2. OR everything is merged into a single binary (and all subpackages except netbird get deprecated);
3. OR their units diverge even further, introducing more incompatibilities.

Whatever comes first.

Can you please explain the rationale behind changing netbird@.service from the default at: https://github.com/netbirdio/netbird/blob/main/release_files/systemd/netbird%40.service

Specifically:

- The invocation command lacks:
  - Logging to file
  - `--daemon-addr` unix socket
  - (the default environment variable is also renamed)
- Two useful comments are removed
- Whitespace is changed

The netbird doco directs people to look in /var/log/netbird/ for log files.

I can understand wanting to log to console, but please don't disable the default, rather add it additionally if you really must change the default logging behaviour.

Consider adding the flag "-x" to the go mod download. It has the benefit of adding correct logs for future reproducible build. https://reproducible.archlinux.org/

Also tells the user about the downloads.

go mod download -x