SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-28 08:52:37 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Add “official” systemd units? #516

New Issue
Closed
opened 2025-11-20 05:12:54 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:12:54 -05:00
Owner
Copy Link

Originally created by @hg on GitHub (Nov 17, 2023).

Hello,

netbird has been maintained in the Arch Linux User repository since 2021, and recently Arch developers have expressed interest in packaging it in the official repository.

Would you be willing to merge hand-rolled systemd .service files instead of (or in addition to) netbird service install?

  • the client config is a templated unit which allows the user to create & start multiple client instances by using systemctl enable --now netbird@foo netbird@bar netbird@baz (the part after the @ matches the name of the config file in /etc/netbird)
  • all units provide partial sandboxing from the rest of the system (#378, although netbird pretty much requires root or CAP_NET_ADMIN these days, they were much stricter in the past). The flags have been there for years and are pretty well tested by now.
  • they can be used by other Linux distributions as the project gets more adoption

The files are here. I can prepare a PR if you're interested, or you can just copy them from there.

If you'd rather stay with netbird service install, Arch (and others in the future) will probably ship their own units.

Thanks.

Originally created by @hg on GitHub (Nov 17, 2023). Hello, netbird has been [maintained](https://aur.archlinux.org/packages/netbird) in the Arch Linux User repository since 2021, and recently Arch developers [have expressed](https://aur.archlinux.org/packages/netbird#comment-944094) interest in packaging it in the official repository. Would you be willing to merge hand-rolled systemd `.service` files instead of (or in addition to) `netbird service install`? - the client config is a templated unit which allows the user to create & start multiple client instances by using `systemctl enable --now netbird@foo netbird@bar netbird@baz` (the part after the `@` matches the name of the config file in `/etc/netbird`) - all units provide partial sandboxing from the rest of the system (#378, although netbird pretty much requires root or `CAP_NET_ADMIN` these days, they were much stricter in the past). The flags have been there for years and are pretty well tested by now. - they can be used by other Linux distributions as the project gets more adoption The files are [here](https://github.com/hg/aur/tree/master/netbird). I can prepare a PR if you're interested, or you can just copy them from there. If you'd rather stay with `netbird service install`, Arch (and others in the future) will probably ship their own units. Thanks.
saavagebueno commented 2025-11-20 05:12:55 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Nov 17, 2023):

Hello @hg this is awesome. We are interested in the PR.

We are organizing the packaging files in the release_files path, but we are open to suggestions to make it clear.

Thanks for reaching out and for maintaining the package in the Arch Linux User repository.

@mlsmaycon commented on GitHub (Nov 17, 2023): Hello @hg this is awesome. We are interested in the PR. We are organizing the packaging files in the [release_files](https://github.com/netbirdio/netbird/tree/main/release_files) path, but we are open to suggestions to make it clear. Thanks for reaching out and for maintaining the package in the Arch Linux User repository.
saavagebueno commented 2025-11-20 05:12:55 -05:00
Author
Owner
Copy Link

@lfarkas commented on GitHub (Nov 22, 2023):

i also vote for a separate service file not the generated one. it'd be much easier on all distro to use the same official service file!

@lfarkas commented on GitHub (Nov 22, 2023): i also vote for a separate service file not the generated one. it'd be much easier on all distro to use the same official service file!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#516
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?