Give more info on "Failed to start <project>: failed to load any docker-compose.*y*l files" for #2049 #2052
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rfay
changed the title
rfay
force-pushed
the
20200127_better_docker_compose_error
branch
from
ce1e40b
to
dd67eec
Compare
rfay
force-pushed
the
20200127_better_docker_compose_error
branch
2 times, most recently
from
3955647
to
11392ff
Compare
rfay
changed the title
rfay
changed the title
rfay
changed the title
rfay
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Problem/Issue/Bug:
We've had a few questions like #2049 where people see errors like "Failed to start my-project: failed to load any docker-compose.yl files:"
So far it's not been easy to track them down.
You can start a project, remove .ddev/docker-compose.yaml, then
ddev exec lsand you'll get it. But most of the time we don't understand.This PR:
A future PR will prevent
ddev configorddev startin directories that have glob patterns in them. That seems too risky for near-release of v1.13.0, and this doesn't happen that often.The simple change of the output should help us with debugging and learning new instances of this problem.
How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:
Related Issue Link(s):
Release/Deployment notes: