-
-
Notifications
You must be signed in to change notification settings - Fork 543
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
docker-compose not working when starting Lando below project root #1007
Comments
try ./docker-compose.yml |
@jbertoen I get the same results when referencing |
Yeah that does seem like a bug, think I found it as well:
If you dissect this This might be the fix. Maybe @pirog or @dustinleblanc have an opinion about this?
|
Got a PR waiting for test results. Hopefully this would fix the issue. |
Any updates on this? Just ran into this issue today myself and it would be good to fix since with the drupal7 recipe one must be in the webroot (below the app root where .lando.yml is) to run drush commands. |
This should be fixed in the forthcoming RC2 |
When I run
lando start
from a level below the project root, the container I've configured in my docker-compose.yml either doesn't start or isn't accessible to Lando.Tell us about your setup
v3.0.0-beta.46 on Mac OSX 10.13.4
Tell us about your
.lando.yml
docker-compose.yml (stored in project root, same level as .lando.yml)
Tell us about the command you were running
Tell us generally about your bug
Should Lando be able to find the
docker-compose.yml
file relative to the.lando.yml
file, rather than relative to where you run the start command? It's defined in the.lando.yml
file. Or is there a way to write the.lando.yml
file to force looking fordocker-compose.yml
relative to the project root?The text was updated successfully, but these errors were encountered: