Skip to content
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

0.9-beta broken for ipv4 only systems #368

Closed
databus23 opened this issue Mar 3, 2017 · 7 comments
Closed

0.9-beta broken for ipv4 only systems #368

databus23 opened this issue Mar 3, 2017 · 7 comments

Comments

@databus23
Copy link
Contributor

We are running k8s on bare metal and don't have the ipv6 kernel model loaded.

With the current beta images this fails with the following error:

Error: exit status 1
nginx: the configuration file /tmp/nginx-cfg712046524 syntax is ok
2017/03/03 14:17:49 [emerg] 280#280: socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /tmp/nginx-cfg712046524 test failed

This obviously comes from this pull request #34

This allows a brave user to run this in host networking mode and support
ipv6.

Unfortunately it seems this breaks the nginx controller for the coward users that don't have ipv6 enabled. :)

/cc @euank @auhlig

@databus23 databus23 changed the title 0.9-beta.1 broken for ipv4 only systems 0.9-beta broken for ipv4 only systems Mar 3, 2017
@pieterlange
Copy link
Contributor

This is merged to master #356

@databus23
Copy link
Contributor Author

@pieterlange from the looks this won't fix the problem. nginx complains about [::]:80 thats not changed in the mentioned commit.

@gianrubio
Copy link
Contributor

@databus23 please take take a look on #371

@aledbf
Copy link
Member

aledbf commented Mar 8, 2017

@databus23 please check if the image quay.io/aledbf/nginx-ingress-controller:0.71 solves the issue.
Contains this fix.

@auhlig
Copy link
Contributor

auhlig commented Mar 8, 2017

Hi @aledbf,
Thanks for looking into this.
I just tested using your image. Unfortunately this does not fix the issue for me. I still get the same "address family not supported" error as @databus23.

2017/03/08 10:23:39 [emerg] 59#59: socket() [::]:80 failed (97: Address family not supported by protocol) nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)

@databus23
Copy link
Contributor Author

@gianrubio I can confirm that #371 fixes this problem.

@PRAJINPRAKASH
Copy link

How fix it in helm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants