Closed jasonevines closed 11 months ago
Looking at the -vvv log, I see this line:
lando 09:39:12 DEBUG ==> process pid5 running /Applications/Docker.app/Contents/Resources/bin/docker exec localsite_app_1 php /usr/local/bin/composer install cstdio=[inherit, pipe, pipe], silent=false, mode=attach, detached=false
Strange that the command is being executed for the an "app_1" service when no such service has been set up.
As troubleshooting steps, I have tried running removing the vendor directory, running lando destroy, and purging Docker data.
If I create a "compose" tooling command, and use that rather than "composer," then everything works fine.
I've been able to duplicate the problem on an Intel Mac as well.
Is there any insight about what's happening here? It's a major usability problem.
Is there a reason you wanted to replace the existing composer
command that comes packaged with all the LAMP-descended recipes (Drupal/WP/etc)?
Following works for me; note that it also works without the added tooling, since the drupal10
recipe has a composer tooling command in it by default:
name: groovy-d10
recipe: drupal10
config:
webroot: web
tooling:
composer:
service: appserver
cmd:
- php /usr/local/bin/composer
@jasonevines I'm guessing this is pretty stale, but definitely re-open the issue if you had more problems/questions around this or DM me on the Lando Slack.
I'm running an M1 Pro Max Macbook Pro, with Lando version 3.6.5 and Docker version 4.8.2. I don't presently have access to an Intel Mac to see whether the error occurs on that platform, too.
The snippet below demonstrates the error when running install, although the problem happens with all composer commands:
Here's how I've set up the tooling command, while trying to troubleshoot:
Here are the results of adding the -vvv flag to "lando composer install:
Running composer commands inside the service shell (after doing lando ssh) works fine, however.