Repository navigation
Conversation
Testcontainers rejects Compose files that set container_name, but the docs did not mention it. Add a note explaining why and what to do. Refs testcontainers#2472
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
What
Starting a
ComposeContainerorDockerComposeContainerwith a Compose file that setscontainer_namefails with anIllegalStateException, but the Docker Compose docs don't mention this. Users only find out at runtime, as reported in #2472.This adds a note to
docs/modules/docker_compose.mdexplaining thatcontainer_nameis not supported, why (each environment runs under a random project name so several can run side by side), and what to do instead.Docs only, no code change. Refs #2472 (the issue also asks for actual support, so it stays open).
🤖 Generated with Claude Code
Summary by CodeRabbit
container_nameon a Docker Compose service can cause Compose startup to fail in tests. The documentation recommends omitting it and referring to containers by their service names instead.