-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Upgrade to version 2.2.0 or higher causes "Address family not supported by protocol" #2970
Comments
Beginning with the 2.2 release a default IPv6 listener is created for nginx. This was to align with K8s making IPv6 a first class citizen and giving controls to administrators to define both IPv4 or IPv6 address pools. Since the determination of whether or not a pod receives an IPv6 address was fully exposed through the K8s cluster configuration, and a pod would not receive an IPv6 address unless an IPv6 address pool was defined, and that that you have to go back quite a few years into unsupported distros to not have an IPv6 stack present - we considered it safe to default to defining an IPv6 listener. If I am understanding your scenario, you are not blocking IPv6 address assignment through the normal networking configuration files, but rather through some method of blocking the IPv6 stack from loading at all at the kernel level of the K8s node. @jppitout, Can you help me understand two things?
That said, and those questions asked, we will be introducing a way to give you more control over the listeners in an upcoming release. And thus fully disable the IPv6 listener if you need to. |
@brianehlert thank you for your response. Some prerequisite knowledge:
For now we'll stick to version NGINX 2.1.2, thanks for clarifying! |
@jppitout Thank you very much for that most excellent explanation. I didn't realize that. |
@brianehlert No problem, I suspect that TKG which uses Cluster API will not have this problem only TKGi which uses BOSH. |
Hi @brianehlert Any feed back on this? We'd like to upgrade to 2.4.0 for other bug fixes but cannot due to this bug. UPDATE |
New command line option added in 2.4 |
Hi @brianehlert, With version 2.4.0 we're still seeing below in the logs even with On the pods themselves we're still seeing ipv6 listeners configured:
Any ideas what could be causing this? |
Describe the bug
On Kubernetes clusters with IPv6 disabled an upgrade to version 2.2.0 and higher causes:
[::]:80 failed (97: Address family not supported by protocol
To Reproduce
Steps to reproduce the behavior:
2022/08/25 12:58:31 [emerg] 12#12: socket() [::]:80 failed (97: Address family not supported by protocol)
Expected behavior
A way to cater for Kubernetes clusters without IPv6 either in the configmap or server-snippets.
We cannot find a way to disable NGINX's IPv6 implementation currently.
Environment
The text was updated successfully, but these errors were encountered: