netbird status -d #2105

Closed
opened 2025-11-20 07:03:56 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @maythazinh on GitHub (Jul 23, 2025).

Environment
Platform: Kubernetes pods with netbird sidecar container
Container: netbirdio/netbird:latest

command = ["/bin/sh"]
args = [
"-c",
<<-EOF
/usr/local/bin/netbird service install
/usr/local/bin/netbird service start
/usr/local/bin/netbird service run &
sleep 10
/usr/local/bin/netbird up --management-url ${local.netbird.management-url} --setup-key ${setupkey}
sleep infinity
EOF
]
env {
name = "NB_FOREGROUND_MODE"
value = "false"
}

Issues Encountered (inside the pod)
/usr/local/bin/netbird service install

Error: open /etc/init.d/netbird: no such file or directory

/usr/local/bin/netbird service start

Error: "rc-service" failed: exec: "rc-service": executable file not found in $PATH

kubectl exec -it pod -c netbird -- netbird status

Error: failed to connect to daemon error: failed to exit idle mode: invalid (non-empty) authority: netbird.sock

OR

Error: failed to connect to daemon error: context deadline exceeded

Question
Is there a container-native way to run netbird with full CLI functionality, or should containers rely only on logs for status monitoring?

Originally created by @maythazinh on GitHub (Jul 23, 2025). Environment Platform: Kubernetes pods with netbird sidecar container Container: netbirdio/netbird:latest command = ["/bin/sh"] args = [ "-c", <<-EOF /usr/local/bin/netbird service install /usr/local/bin/netbird service start /usr/local/bin/netbird service run & sleep 10 /usr/local/bin/netbird up --management-url ${local.netbird.management-url} --setup-key ${setupkey} sleep infinity EOF ] env { name = "NB_FOREGROUND_MODE" value = "false" } Issues Encountered (inside the pod) /usr/local/bin/netbird service install # Error: open /etc/init.d/netbird: no such file or directory /usr/local/bin/netbird service start # Error: "rc-service" failed: exec: "rc-service": executable file not found in $PATH kubectl exec -it pod -c netbird -- netbird status # Error: failed to connect to daemon error: failed to exit idle mode: invalid (non-empty) authority: netbird.sock # OR # Error: failed to connect to daemon error: context deadline exceeded Question Is there a container-native way to run netbird with full CLI functionality, or should containers rely only on logs for status monitoring?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2105