DYNR/netbird
2
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-05 00:15:26 -04:00
Code Issues 23.5k Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #569] A couple of questions and feedback #1060

New Issue
Open
opened 2026-08-05 00:41:01 -04:00 by saavagebueno · 0 comments
saavagebueno commented 2026-08-05 00:41:01 -04:00
Owner
Copy Link

Originally created by @tvarsis on GitHub (Nov 19, 2022).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/569

I have tried to set this up following your self-hosting docker instructions, and have come across some issues and have a couple of questions and feedback. I'm opening an issue about them, since I could not find any information about these in the documentation or in other issues, so could be good to get it documented here.

  1. In the generated management.json file, this row exists: "Secret": "secret". I tried to figure out what that does, and maybe it is not used at all, but it gives the impression of a value that should be changed or else insecure, right?
  2. docker-compose file uses host network for coturn container. That is usually bad practice. Should it not be possible to avoid that and rely on docker network where you just expose needed services to the host instead of using the host network layer?
  3. Setting up OIDC provider usually requires both client id and secret together with the discovery endpoint. But I can't find anywhere to add the secret?
  4. Is there any documentation how to run this behind a regular nginx reverse proxy? I'm not a fan of having docker-compose files that "includes everything", since that will mess up other web services running on the same host. I think most people that self-host run some kind of reverse proxy in front of their docker stuff, so some documentation or alternative docker-compose file for those cases would be awesome.
  5. After following the guide, I ended up with this error from docker-compose up, which indicates some permission issues:
ERROR: for infrastructure_files_coturn_1  Cannot start service coturn: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: errCreating infrastructure_files_management_1 ... done

ERROR: for coturn  Cannot start service coturn: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open /proc/sys/kernel/domainname: permission denied: unknown
ERROR: Encountered errors while bringing up the project.
  1. Since you support OIDC standard, I guess this would work with any such provider, right? Documentation seems to indicate that it does not. Also, callback url is hard to find any information about which needs to be provided when configuring the OIDC on the provider side.

I think this project is really cool and hope it gets good traction, so the above points are meant in good faith in hope to improve some current pain points.

Thanks!

Originally created by @tvarsis on GitHub (Nov 19, 2022). Original GitHub issue: https://github.com/netbirdio/netbird/issues/569 I have tried to set this up following your self-hosting docker instructions, and have come across some issues and have a couple of questions and feedback. I'm opening an issue about them, since I could not find any information about these in the documentation or in other issues, so could be good to get it documented here. 1. In the generated management.json file, this row exists: "Secret": "secret". I tried to figure out what that does, and maybe it is not used at all, but it gives the impression of a value that should be changed or else insecure, right? 2. docker-compose file uses host network for coturn container. That is usually bad practice. Should it not be possible to avoid that and rely on docker network where you just expose needed services to the host instead of using the host network layer? 3. Setting up OIDC provider usually requires both client id and secret together with the discovery endpoint. But I can't find anywhere to add the secret? 4. Is there any documentation how to run this behind a regular nginx reverse proxy? I'm not a fan of having docker-compose files that "includes everything", since that will mess up other web services running on the same host. I think most people that self-host run some kind of reverse proxy in front of their docker stuff, so some documentation or alternative docker-compose file for those cases would be awesome. 5. After following the guide, I ended up with this error from docker-compose up, which indicates some permission issues: ``` ERROR: for infrastructure_files_coturn_1 Cannot start service coturn: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: errCreating infrastructure_files_management_1 ... done ERROR: for coturn Cannot start service coturn: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open /proc/sys/kernel/domainname: permission denied: unknown ERROR: Encountered errors while bringing up the project. ``` 6. Since you support OIDC standard, I guess this would work with any such provider, right? Documentation seems to indicate that it does not. Also, callback url is hard to find any information about which needs to be provided when configuring the OIDC on the provider side. I think this project is really cool and hope it gets good traction, so the above points are meant in good faith in hope to improve some current pain points. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2021 Q4
2021 Q4
2022 Q1
2022 Q1
2022 Q1
2022 Q1
2022 Q1
2022 Q1
accessibility
accessibility
accessibility
acl
acl
acl
agent
agent
agent
agent
agent
agent
Android
Android
Android
Android
Android
Android
api
api
api
authentik
authentik
authentik
automation
automation
automation
azure
azure
azure
battery-usage
battery-usage
battery-usage
bug
cache
cache
cache
client
client
client
client-ui
client-ui
client-ui
cloud
cloud
cloud
cloud-only
cloud-only
cloud-only
cloudflare
cloudflare
cloudflare
community
community
community
compatibility
compatibility
compatibility
config-idp
config-idp
config-idp
config-issue
config-issue
config-issue
connection
connection
connection
contribution
contribution
contribution
coturn
coturn
coturn
cross-vpn
cross-vpn
cross-vpn
dashboard
dashboard
dashboard
data-usage
data-usage
data-usage
distribution
distribution
distribution
dns
dns
dns
docker
docker
docker
documentation
documentation
documentation
duplicate
duplicate
duplicate
enhancement
enhancement
event-stream
event-stream
event-stream
feature-request
feature-request
feature-request
freebsd
freebsd
freebsd
getting-started
getting-started
getting-started
go
go
go
good first issue
good first issue
good first issue
gui
gui
gui
help wanted
help wanted
help wanted
home-assistant
home-assistant
home-assistant
idp
idp
idp
inconsistency
inconsistency
inconsistency
integration
integration
integration
integrations
integrations
integrations
ios
ios
ios
ipv6
ipv6
ipv6
jwt
jwt
jwt
k8s
k8s
k8s
keycloak
keycloak
keycloak
linux
linux
linux
login
login
login
macos
macos
macos
management-service
management-service
management-service
Medium
Medium
Medium
missing-docs
missing-docs
missing-docs
mobile
mobile
mobile
moved-internal
moved-internal
moved-internal
needs-review
needs-review
needs-review
netbird-ui
netbird-ui
netbird-ui
networking
networking
networking
new-platform
new-platform
new-platform
nginx
nginx
nginx
notification
notification
notification
okta
okta
okta
openwrt
openwrt
openwrt
P2
P2
P2
packaging
packaging
packaging
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
peer-management
performance
performance
performance
postgres
postgres
postgres
posture-checks
posture-checks
posture-checks
psk
psk
psk
pull-request
Mirrored from GitHub Pull Request
 question
question
question
refactor
refactor
refactor
relay
relay
relay
release
release
release
rfc
rfc
rfc
routes
routes
routes
security
security
security
security-improvement
security-improvement
security-improvement
security-related
security-related
security-related
self-hosting
self-hosting
self-hosting
server
server
server
signal
signal
signal
sleep-issue
sleep-issue
sleep-issue
ssh
ssh
ssh
ssl
ssl
ssl
status
status
status
store
store
store
synology
synology
synology
system-compatibility-issue
system-compatibility-issue
system-compatibility-issue
test-suite
test-suite
test-suite
third-party-integration
third-party-integration
third-party-integration
triage
triage
triage
triage
triage
triage
triage-needed
triage-needed
triage-needed
troubleshooting
troubleshooting
troubleshooting
UX
UX
UX
waiting-feedback
waiting-feedback
waiting-feedback
windows
windows
windows
wontfix
wontfix
wontfix
zitadel
zitadel
zitadel
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dynr-servers saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#1060
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?