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

Compose should use compose_file_name=[] or None by default #259

Open
bitplane opened this issue Oct 25, 2022 · 2 comments
Open

Compose should use compose_file_name=[] or None by default #259

bitplane opened this issue Oct 25, 2022 · 2 comments

Comments

@bitplane
Copy link
Contributor

bitplane commented Oct 25, 2022

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

@tillahoffmann
Copy link
Collaborator

Thanks for reporting. Do you have a code snippet to illustrate the issue?

@bitplane
Copy link
Contributor Author

It was part of a project I was working on for a customer so can't really share. If I find time I'll create a test case, and if I have a failing test then I guess I might as well fix it and send a PR too. No promises at the moment as it's bottom of my priorities, so if anyone else wants to do it go for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants