-
Notifications
You must be signed in to change notification settings - Fork 109
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
Pact Broker does not bind to [::]
, only 0.0.0.0
#163
Comments
Thanks for the report. If you would like to submit the PR to fix this, I will approve it. |
The port is variable, btw, so the bind will need to go in https://github.com/pact-foundation/pact-broker-docker/blob/master/pact_broker/config/puma.rb and not be hardcoded to 9292 |
Docs for bind https://www.rubydoc.info/gems/puma/Puma%2FDSL:bind which will replace the port https://www.rubydoc.info/gems/puma/Puma/DSL#port-instance_method in the config file |
The most recent release should support IPv6 any. Please try it out and let me know. |
Release should be out shortly, we had a couple of issues holding it back but they've been resolved now (failing audit and gem update) |
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):Software versions
Expected behaviour
Pact broker binds to ipv6 "any" address.
Actual behaviour
The containerized pact broker is not reachable in an ipv6-only environment.
Steps to reproduce
Context
See also: https://pact-foundation.slack.com/archives/C9VPNUJR2/p1706574031623059
We're moving to ipv6-only kubernetes clusters.
We're using https://github.com/pact-foundation/pact-broker-docker via the https://github.com/pact-foundation/pact-broker-chart.
The container was failing to be reachable, because puma was only binding to the ipv4 port. We saw this by kubectl execing in and running
netstat -nl
:This is resolved by modifying
entrypoint.sh
to readbundle exec puma --bind 'tcp://[::]:9292'
(note:--bind 'tcp://[::]' --port 9292
does NOT work.)Then we get:
and everything works.
Ideally, I think puma should bind to both the ipv4 and ipv6 "any" addresses.
The text was updated successfully, but these errors were encountered: