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

Clear docker compose initialization #9370

Merged
merged 9 commits into from
Oct 10, 2024
Merged

Clear docker compose initialization #9370

merged 9 commits into from
Oct 10, 2024

Conversation

eddumelendez
Copy link
Member

Currently, an instance of DockerComposeContainer and ComposeContainer keep information from previous initialization which causes issues when running the instance more than once.

Fixes #7443

JenoDK and others added 8 commits August 29, 2023 13:37
Currently, an instance of `DockerComposeContainer` and `ComposeContainer`
keep information from previous initialization which causes issues when
running the instance more than once.

Fixes #7443
@eddumelendez eddumelendez merged commit 94e4c85 into main Oct 10, 2024
104 checks passed
@eddumelendez eddumelendez deleted the gh-7443 branch October 10, 2024 02:09
agebhar1 added a commit to agebhar1/eventbridge-kafka-connector that referenced this pull request Oct 31, 2024
With [tc-gh9370] Docker compose initialization is cleared. The shared (static)
Docker compose instance is not valid in successive tests anymore.

Fixed it by running Docker compose for each test class.

[tc-gh9370]: testcontainers/testcontainers-java#9370
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: DockerComposeContainer with healthcheck wait strategy fails for successive tests
2 participants