Switch destination hasura url config to 127.0.0.1 to avoid ipv6 #343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It appears that Node 18, which we recently moved to, favors IPv6 resolution. Given that Airbyte spawns sources and destinations as containers that run outside the Faros CE compose, this causes issues when the destination tries to connect to hasura on
::1:8080
instead of127.0.0.1:8080
. Not sure exactly why - more docker networking expertise needed.So the current fix is just to switch from
localhost
to an explicit IPv4127.0.0.1
in the destination settings, which works.I am not touching other localhosts in the environment variables, as this behavior appears to be specific to code running on Node in a container. I also check that the mock-data scripts are unaffected (they do not run in a container).
Type of change
(Delete what does not apply)
Checklist
(Delete what does not apply)