-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
netbox ipv6 listens #220
Comments
This is a changed that happened in the upstream docker image. We've had reports of it failing both on IPv6-only clusters and IPv4-only clusters. (sigh 😅) The good news is that you can update it to work however you want using the overrideUnitConfig section of This will probably be a more common problem over time, we should update the docs to talk about it. |
Ah. Perfect. Will give that a try. Thanks! :) |
Having the same issue here. How would be the right way to set it trough a |
@kikem4n Using your own # values.yaml
overrideUnitConfig:
{
"listeners": {
"0.0.0.0:8080": {
"pass": "routes/main"
},
# Remove below lines
"[::]:8080": {
"pass": "routes/main"
},
"0.0.0.0:8081": {
"pass": "routes/status"
},
# Remove these too
"[::]:8081": {
"pass": "routes/status"
}
},
# ... Rest of the config from https://github.com/netbox-community/netbox-docker/blob/release/docker/nginx-unit.json
} Then provide your helm install netbox oci://ghcr.io/netbox-community/netbox-chart/netbox -f values.yaml |
For your information, this has been documented on the Docker image wiki: https://github.com/netbox-community/netbox-docker/wiki/Troubleshooting#netbox-container-doesnt-start-when-ipv6-is-disabled With the use of netbox-chart/charts/netbox/values.yaml Lines 476 to 516 in 190868c
Closing in favor of netbox-community/netbox-docker#997 & netbox-community/netbox-docker#925 |
We tried to deploy
netbox-5.0.0-beta13
on a cluster that has ipv6 totally disabled. It fails to listen on the [::] rules. Can those be made configurable?The text was updated successfully, but these errors were encountered: