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

chef-zero binds to ::1 even if you disable IPv6 #48

Open
balasankarc opened this issue Jan 5, 2017 · 1 comment
Open

chef-zero binds to ::1 even if you disable IPv6 #48

balasankarc opened this issue Jan 5, 2017 · 1 comment

Comments

@balasankarc
Copy link

In regard to https://gitlab.com/gitlab-org/omnibus-gitlab/issues/576 .

Even if ipv6 is disabled in system, chef-zero binds to ::1, and makes omnibus-ctl take too much time. Fixed it with running chef-client with --chef-zero-host 127.0.0.1 option.

Is this a valid fix? What are the thoughts on a PR to omnibus-ctl's use of chef-client?

@smith
Copy link
Contributor

smith commented Jan 5, 2017

Is there a (cross-platform, in Ruby or otherwise) way to check if ipv6 is enabled on a system and conditionally set this option? Seems like using ipv6 by default is the right thing to do in the long term, but falling back to v4 if necessary would be good too.

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

2 participants