testcontainers / testcontainers/testcontainers-python
Compose should use `compose_file_name=[]` or `None` by default
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 386
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
For some reason docker-compose up -d works subtly differently than docker-compose up -d -f docker-compose.yml when there are overrides files. I'm not sure why, but passing compose_file_name=[] fixes things for me locally as it doesn't build the -f list.
I think this should be the default, rather than defaulting to a specific file name.
Also, since it actually supports a list, the parameter name should be different so this is obvious
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the compose_file_name parameter and the code that builds the docker-compose command's -f list. Compare the default behavior with an explicit empty list or None, and check how the parameter is used elsewhere before deciding whether its name should change. Done means default invocation handles override files consistently and the supported list value is clearly represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100