Skip to content

Conversation

@henri-tremblay
Copy link
Contributor

When a docker-compose.yml file start to rely heavily on aliases, we can go above the default maximum of 50. It happened to me. There is no way to override it. We would need to inject LoaderOptions, ParsedDockerComposeFile, DockerComposeFiles and DockerComposeContainer. I don't want to go there.

So instead, I have set a reasonable threshold. I can't see any harm in having it.

This is all in the last commit.

Other commits are fixing things I wanted to improve in a boy scout style.

@henri-tremblay henri-tremblay requested a review from a team June 27, 2024 19:54
@henri-tremblay henri-tremblay force-pushed the bigger-max-aliases branch 3 times, most recently from be26044 to db52bd0 Compare June 27, 2024 22:13
@eddumelendez
Copy link
Member

more than 50 services in a docker compose file? 🤯

@henri-tremblay
Copy link
Contributor Author

:-) It's actually the aliases the problem. So the <<: *entry. It you use different ones, it's not that hard to reach 50. But in my case, yes, I have more than 50 services.

@eddumelendez eddumelendez merged commit e2941dc into testcontainers:main Jul 1, 2024
@eddumelendez
Copy link
Member

Thanks for your contribution, @henri-tremblay !

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.

2 participants