Closed alex-r-redfern closed 4 months ago
To add: docker version: Docker version 26.0.1, build d260a54
Further point of interest: Running rebuilds back to back errors out on different services each time:
lando rebuild -y
Rising anew like a fire phoenix from the ashes! Rebuilding app...
ERROR: The Compose file '/home/alex/.lando/compose/projectnamehere/globals-0.yml' is invalid because:
Unsupported config option for services: 'redis'
ERROR ==>
lando rebuild -y
Rising anew like a fire phoenix from the ashes! Rebuilding app...
ERROR: The Compose file '/home/alex/.lando/compose/projectnamehere/globals-0.yml' is invalid because:
Unsupported config option for services: 'meilisearch'
ERROR ==>
lando rebuild -y
Rising anew like a fire phoenix from the ashes! Rebuilding app...
ERROR: The Compose file '/home/alex/.lando/compose/projectnamehere/globals-0.yml' is invalid because:
Unsupported config option for services: 'appserver'
ERROR ==>
lando rebuild -y
Rising anew like a fire phoenix from the ashes! Rebuilding app...
ERROR: The Compose file '/home/alex/.lando/compose/projectnamehere/globals-0.yml' is invalid because:
Unsupported config option for services: 'appserver'
ERROR ==>
After a tip from Steve on the Slack, I ran lando setup --skip-common-plugins
and it shows that docker compose is no longer installed:
THING STATUS COMMENT
─────────────────────────────────────── ─────────────── ───────────────────────────────────
@lando/build-engine (docker-engine) ✔ Installed Dialed
@lando/build-engine-group (alex@docker) ✔ Installed Dialed
@lando/orchestrator (docker-compose) ⚠ Not Installed Will install docker-compose v2.26.1
This resolved the issue. I'm happy for this to be closed, but feel free to re-open if this is an actual underlying bug and not an os/platform issue.
Just a thought, but might be worth adding a startup check to ensure engine and compose are installed as to avoid ambiguous error messages.
Yeah I've been seeing a steady trickle of people missing the requirement to install the prereqs now that we're not using installers on Mac/Windows. If you try to run Lando and don't have Docker, you get an error relating to Lando's inability to spin up Docker, which is fairly definitive, but I think there are other cases like yours that can show up.
In your case, do you know what version of Lando you updated from? Wondering if you had an older version that used Docker Compose v1, and that the update to 3.21 created a mismatch between the version of Docker Compose installed and what was needed.
Ah, so it will be about 4 weeks old, but interestingly the terminal I use is very short (phpstorm built in) so content can be scrolled past easily, and if I recall correctly there was some additional output other than the warning after the update which may have pushed it up and out of view. Apologies, I didn't screenshot this at the time. I wouldn't sweat this issue too much as I'm sure if anyone ends up in the same boat they'll find this ticket hopefully. Thanks to you and the rest of the team at Lando for the amazing work :)
Thanks @alex-r-redfern, appreciate the kind words!
Hmm, I'm on Linux and seeing this, if that's of interest (looking at https://github.com/lando/core/issues/153#issuecomment-2075529898).
AFAICT the previous lando setup
command did not have any warning about @lando/orchestrator
, nor did it attempt to update it.
$ lando update
Generating plugin/cli update matrix... done [see table below]
PACKAGE STATUS COMMENT
──────────────────── ────────────────── ─────────────────────────────────────────────────────────
@lando/acquia ✔ Up to date All good
@lando/apache ✔ Up to date All good
@lando/backdrop ✔ Up to date All good
@lando/cli ⚠ Update available https://github.com/lando/cli/releases/tag/v3.21.0-beta.14
@lando/compose ✔ Up to date All good
@lando/core ✔ Up to date All good
@lando/dotnet ✔ Up to date All good
@lando/drupal ✔ Up to date All good
@lando/elasticsearch ✔ Up to date All good
@lando/go ✔ Up to date All good
@lando/healthcheck ✔ Up to date All good
@lando/joomla ✔ Up to date All good
@lando/lagoon ✔ Up to date All good
@lando/lamp ✔ Up to date All good
@lando/laravel ✔ Up to date All good
@lando/lemp ✔ Up to date All good
@lando/mailhog ✔ Up to date All good
@lando/mariadb ✔ Up to date All good
@lando/mean ✔ Up to date All good
@lando/memcached ✔ Up to date All good
@lando/mongo ✔ Up to date All good
@lando/mssql ✔ Up to date All good
@lando/mysql ✔ Up to date All good
@lando/networking ✔ Up to date All good
@lando/nginx ✔ Up to date All good
@lando/node ✔ Up to date All good
@lando/pantheon ✔ Up to date All good
@lando/php ✔ Up to date All good
@lando/phpmyadmin ✔ Up to date All good
@lando/platformsh ⚠ Cannot update Please update manually.
@lando/postgres ⚠ Cannot update Please update manually.
@lando/proxy ✔ Up to date All good
@lando/python ✔ Up to date All good
@lando/redis ✔ Up to date All good
@lando/ruby ✔ Up to date All good
@lando/scanner ✔ Up to date All good
@lando/sharing ✔ Up to date All good
@lando/solr ✔ Up to date All good
@lando/symfony ✔ Up to date All good
@lando/tomcat ✔ Up to date All good
@lando/varnish ✔ Up to date All good
@lando/wordpress ✔ Up to date All good
Lando would like to update 1 package(s) listed above.
DO YOU CONSENT?: y
✔ Updated @lando/cli to 3.21.0-beta.14
Updated 1 of 1 packages successfully!
You are now up to date! with the latest and greatest!
However, running the command from https://github.com/lando/core/issues/153#issuecomment-2069783541 did address the issue it seems.
lando setup --skip-common-plugins
Lando version: v3.21.0-beta.15 Host: Ubuntu/Mint - Linux 6.5.0-27
Issue: After updating Lando core, rebuilds and destroys all fail. Manually deleting containers/images/volumes in docker does not resolve this, nor does manually removing configuration files in ~/.lando/compose. The projects all started / rebuild successfully prior to this update.
Terminal output:
Lando file for project:
I'm unsure how to proceed in diagnosing this further and would hugely appreciate any further advice.
Thanks, Alex