netbox container fails to start on ipv6 disabled hosts, though ipv6 listener is disabled #1614
Answered
by
necarnot
necarnot
asked this question in
Getting Help
-
Current BehaviorI'm running netbox-docker for years and upgrading at each release with no major issues. Years ago, I've already included an override of nginx conf file in my docker-compose.override.yml file : which nginx-unit.json contains a listener section with ipv6 section removed. So it was OK. Now, I see in the release notes (https://github.com/netbox-community/netbox-docker/releases) that the internal nginx is replaced by granian (I'm light years from having understood what I just wrote), and I'm wondering if this could explain the issue described above. Expected BehaviorI wish the netbox container would run as usual. Docker Compose Version
Docker VersionThe git RevisionThe git StatusStartup Commanddocker compose up NetBox LogsContent of docker-compose.override.ymlservices:
netbox:
security_opt:
- seccomp:unconfined
ports:
- 8000:8080
healthcheck:
start_period: 240s
test: "curl -f http://127.0.0.1:8080/login/ || exit 1"
environment:
REMOTE_AUTH_ENABLED: "True"
REMOTE_AUTH_BACKEND: "netbox.authentication.LDAPBackend"
AUTH_LDAP_SERVER_URI: "REDACTED"
AUTH_LDAP_BIND_DN: "REDACTED"
AUTH_LDAP_BIND_PASSWORD: "REDACTED"
AUTH_LDAP_USER_SEARCH_BASEDN: "REDACTED"
AUTH_LDAP_GROUP_SEARCH_BASEDN: "REDACTED"
AUTH_LDAP_REQUIRE_GROUP_DN: "REDACTED"
AUTH_LDAP_GROUP_TYPE: "NestedGroupOfNamesType"
AUTH_LDAP_IS_ADMIN_DN: "REDACTED"
LDAP_IGNORE_CERT_ERRORS: "true"
CSRF_TRUSTED_ORIGINS: "REDACTED"
GRANIAN_HOST: "0.0.0.0"
restart: unless-stopped
volumes:
- /data/projects/nginx-unit.json:/etc/unit/nginx-unit.json:ro
netbox-worker:
healthcheck:
start_period: 120s
restart: unless-stopped
postgres:
restart: unless-stopped
redis:
restart: unless-stopped
redis-cache:
restart: unless-stopped |
Beta Was this translation helpful? Give feedback.
Answered by
necarnot
Feb 6, 2026
Replies: 1 comment 3 replies
-
|
You can change the hosts Granian listens on in this file: https://github.com/netbox-community/netbox-docker/blob/release/docker/launch-netbox.sh |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Thank you for this pointer, @tobiasge . My two cents, but.. I don't think I'm the only one to disable ipv6 on his hosts, so this workaround could be legitimately be mentioned in the upgrade notes when switching from nginx to granian. |
Beta Was this translation helpful? Give feedback.
Answer selected by
tobiasge
-
|
I've added the solution here: https://github.com/netbox-community/netbox-docker/wiki/Troubleshooting#netbox-container-doesnt-start-when-ipv6-is-disabled |
Beta Was this translation helpful? Give feedback.
-
@tobiasge You're the man :) |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for this pointer, @tobiasge .
This helped me to override the --host option we can see in the file you're pointing to, by using the following environment setup :
My two cents, but.. I don't think I'm the only one to disable ipv6 on his hosts, so this workaround could be legitimately be mentioned in the upgrade notes when switching from nginx to granian.