You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying the self-hosted NetBird management service in a Kubernetes environment, and configuring PostgreSQL as the storage backend (via NETBIRD_STORE_TYPE=postgres and NETBIRD_STORE_ENGINE_POSTGRES_DSN=...), the main database works correctly with PostgreSQL.
However, even in this setup, a local event.db SQLite file is still created inside the management container's filesystem. This suggests that the event database (eventDB) does not follow the same configuration and silently defaults to SQLite.
This behavior becomes problematic in production Kubernetes deployments, where container filesystems are ephemeral. As a result, whenever the manager Pod is restarted, the event.db file is lost, and with it, any events or logs stored in it. This leads to a loss of observability and historical data, which is critical for auditing and debugging purposes in production environments.
To Reproduce
Deploy netbird/management with NETBIRD_STORE_TYPE=postgres and NETBIRD_STORE_DATA_SOURCE set correctly.
Start the pod and verify PostgreSQL is used.
Observe that a local event.db file is still created in the container.
Logs do not indicate a switch to PostgreSQL for event storage.
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Are you using NetBird Cloud?
self-host NetBird's control plane.
NetBird version
0.43
Is any other VPN software installed?
no
Debug output
netbird status -dA
As well as the file created by
netbird debug for 1m -AS
We advise reviewing the anonymized output for any remaining personal information.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Have you tried these troubleshooting steps?
Checked for newer NetBird versions
Searched for similar issues on GitHub (including closed ones)
Restarted the NetBird client
Disabled other VPN software
Checked firewall settings
The text was updated successfully, but these errors were encountered:
Describe the problem
When deploying the self-hosted NetBird management service in a Kubernetes environment, and configuring PostgreSQL as the storage backend (via NETBIRD_STORE_TYPE=postgres and NETBIRD_STORE_ENGINE_POSTGRES_DSN=...), the main database works correctly with PostgreSQL.
However, even in this setup, a local event.db SQLite file is still created inside the management container's filesystem. This suggests that the event database (eventDB) does not follow the same configuration and silently defaults to SQLite.
This behavior becomes problematic in production Kubernetes deployments, where container filesystems are ephemeral. As a result, whenever the manager Pod is restarted, the event.db file is lost, and with it, any events or logs stored in it. This leads to a loss of observability and historical data, which is critical for auditing and debugging purposes in production environments.
To Reproduce
Deploy netbird/management with NETBIRD_STORE_TYPE=postgres and NETBIRD_STORE_DATA_SOURCE set correctly.
Start the pod and verify PostgreSQL is used.
Observe that a local event.db file is still created in the container.
Logs do not indicate a switch to PostgreSQL for event storage.
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Are you using NetBird Cloud?
self-host NetBird's control plane.
NetBird version
0.43
Is any other VPN software installed?
no
Debug output
netbird status -dA
As well as the file created by
netbird debug for 1m -AS
We advise reviewing the anonymized output for any remaining personal information.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Have you tried these troubleshooting steps?
The text was updated successfully, but these errors were encountered: