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

Backport of test: force IPv4 on Docker 26+ to fix Envoy int tests into release/1.17.x #20989

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #20986 to be assessed for backporting due to the inclusion of the label backport/1.17.

The below text is copied from the body of the original PR.


As of Docker Engine 26.0.0 (moby/moby#47062), IPv6 is enabled by default where supported. This causes issues for our tests attempting to resolve requests to other containers over localhost, since on Linux IPv6 will be preferred over IPv4 when available when applying the default behavior defined in RFC3484.

As a workaround, force IPv4 with a flag passed to docker run.

Testing & Reproduction steps

CI continues to pass (Docker Engine version is still <26 on runners used for CE builds).

Links

moby/moby#47062

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/zalimeni/fix-envoy-int-tests-docker-26-force-ipv4/brightly-classic-lioness branch from fbb5b5a to 81c5806 Compare April 17, 2024 19:50
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@zalimeni zalimeni merged commit 262ea17 into release/1.17.x Apr 17, 2024
96 checks passed
@zalimeni zalimeni deleted the backport/zalimeni/fix-envoy-int-tests-docker-26-force-ipv4/brightly-classic-lioness branch April 17, 2024 20:14
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

Successfully merging this pull request may close these issues.

None yet

3 participants