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
My test stand has postgresql and redis running as Docker containers (docker.io/postgres:16-alpine and docker.io/redis:7-alpine). Netbox is installed in k8s via helm chart that is using netboxcommunity/netbox images.
Netbox containers connect to external redis and postgresql fine. Migrations are working. App is running.
Contrast to Current Behavior
In my case when trying to start a container migration check fails:
django.db.utils.OperationalError: connection failed: %IP%), port 5432 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
At the same time if I telnet or psql to db from the same host (or even ./manage.py dbshell) it is working fine.
Required Changes
If going inside the container, activating venv and upgrading psycopg from 3.1.16 to 3.1.18 only then ./manage migrate start's working.
Please bump the version in requirements-container.txt
Discussion: Benefits and Drawbacks
Why is it different from requirements.txt anyway?
The text was updated successfully, but these errors were encountered:
We changed the dependency because Netbox uses the binary install and not the compiled version. But there is a PR to change that: netbox-community/netbox#15468
Then we will remove the extra dependency from the image. The next release will contain version 3.1.18 (it's already in the develop branch).
@tobiasge thanks!
Are you talking about the next release of Netbox, that is v4.0? Or you are talking about the next netbox-docker release that might be before that?
Desired Behavior
My test stand has postgresql and redis running as Docker containers (
docker.io/postgres:16-alpine
anddocker.io/redis:7-alpine
). Netbox is installed in k8s via helm chart that is usingnetboxcommunity/netbox
images.Netbox containers connect to external redis and postgresql fine. Migrations are working. App is running.
Contrast to Current Behavior
In my case when trying to start a container migration check fails:
At the same time if I
telnet
orpsql
to db from the same host (or even./manage.py dbshell
) it is working fine.Required Changes
If going inside the container, activating venv and upgrading
psycopg
from3.1.16
to3.1.18
only then./manage migrate
start's working.Please bump the version in
requirements-container.txt
Discussion: Benefits and Drawbacks
Why is it different from
requirements.txt
anyway?The text was updated successfully, but these errors were encountered: