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

Expose test containers' hostnames on custom networks #14855

Merged
merged 1 commit into from
Nov 2, 2022

Conversation

jacobbaskin
Copy link
Contributor

Description

On some Docker environment, tests that rely on communication between Docker containers using a custom
network (e.g. those using HiveMinioDataLake) fail. This change ensures that, in this situation, containers
are always configured to expose their hostname as a DNS alias over Docker custom networks.

Non-technical explanation

Ensure that tests using multiple Docker containers are reproducible on non-continuous-build environments

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

@jacobbaskin jacobbaskin force-pushed the network-alias-testcontainers branch from aa32313 to 8a7643d Compare November 1, 2022 19:14
@cla-bot cla-bot bot added the cla-signed label Nov 1, 2022
@hashhar hashhar merged commit 0326cd5 into trinodb:master Nov 2, 2022
@github-actions github-actions bot added this to the 402 milestone Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants