-
Notifications
You must be signed in to change notification settings - Fork 106
docker-compose auto-detection brittle #153
Comments
It is indeed hacky :) To be fair, we haven't seen too many issues with it. What did your file look like? Is there any easy fix we could put in to take care of it? Another simple improvement would be to log a warning if a |
Thanks, @brikis98. It looked something like this:
I guess it wouldn't be too hard to recognize comments. Yes, what would have helped me a lot is if the log message said something like:
Instead of:
That way someone can know that the compose file was being found but just that no paths were parsed out. |
Both fixes seem useful. PRs are more than welcome :) |
Okay, if I have time, I'll do it. :) By the way, I just noticed that if you pass explicit sync paths using the |
(To clarify, it merges these lists, using both the explicitly passed sync paths in addition to what is in the compose file.) |
I don't think there is a parameter to specifically ignore the compose file, but you could just the compose file path with the |
The documentation in the README says:
However, when I run
docker-osx-dev
from a directory that containsdocker-compose.yml
, it sometimes doesn't notice the file:Looking at the code, I see why now:
docker-osx-dev/src/docker-osx-dev
Line 894 in c4df976
I had YAML comments in my file that broke the hacky parsing.
The lack of true support should be better documented to save people time.
The text was updated successfully, but these errors were encountered: