You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
For some reason
docker-compose up -d
works subtly differently thandocker-compose up -d -f docker-compose.yml
when there are overrides files. I'm not sure why, but passingcompose_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
The text was updated successfully, but these errors were encountered: