-
-
Notifications
You must be signed in to change notification settings - Fork 9
Description
I'm on Windows 11 and I installed the latest version of Lando v3.21.2 using these instructions: https://docs.lando.dev/install/windows.html#advanced
I already had version v3.20.4 installed, which was removed by the PowerShell installation script.
I have a drupal10 recipe that has worked flawlessly on v3.20.4.
After updating Lando to v3.21.2, I ran lando destroy to remove everything and then ran lando rebuild, but I get this error:
WARN ==> drupal10 is not a supported recipe type.
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
Error: Could not find a service builder called drupal10 in the builder registry!
at Factory.get (C:\snapshot\cli\node_modules\@lando\core\lib\factory.js)
at C:\snapshot\cli\node_modules\@lando\core\hooks\app-add-recipes.js
at AsyncEvents.<anonymous> (C:\snapshot\cli\node_modules\@lando\core\app.js)
From previous event:
at AsyncEvents.handle (C:\snapshot\cli\node_modules\@lando\core\lib\events.js)
at C:\snapshot\cli\node_modules\@lando\core\lib\events.js
at process.processImmediate (node:internal/timers:476:21)
From previous event:
at AsyncEvents.emit (C:\snapshot\cli\node_modules\@lando\core\lib\events.js)
at C:\snapshot\cli\node_modules\@lando\core\lib\app.js
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Node.js v18.19.1
I ran lando update for the first time and got this:
$ lando update
Generating plugin/cli update matrix... done [nothing to update]
PACKAGE STATUS COMMENT
────────────────── ──────────── ────────
@lando/cli ✔ Up to date All good
@lando/core ✔ Up to date All good
@lando/healthcheck ✔ Up to date All good
@lando/networking ✔ Up to date All good
@lando/proxy ✔ Up to date All good
@lando/scanner ✔ Up to date All good
@lando/sharing ✔ Up to date All good
As far as lando update can tell you are already up to date!
I ran lando setup and got this:
WARN ==> drupal10 is not a supported recipe type.
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
Error: Could not find a service builder called drupal10 in the builder registry!
at Factory.get (C:\snapshot\cli\node_modules\@lando\core\lib\factory.js)
at C:\snapshot\cli\node_modules\@lando\core\hooks\app-add-recipes.js
at AsyncEvents.<anonymous> (C:\snapshot\cli\node_modules\@lando\core\app.js)
From previous event:
at AsyncEvents.handle (C:\snapshot\cli\node_modules\@lando\core\lib\events.js)
at C:\snapshot\cli\node_modules\@lando\core\lib\events.js
at process.processImmediate (node:internal/timers:476:21)
From previous event:
at AsyncEvents.emit (C:\snapshot\cli\node_modules\@lando\core\lib\events.js)
at C:\snapshot\cli\node_modules\@lando\core\lib\app.js
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
I ran lando update --debug and now I get this:
$ lando update --debug
lando starting 'lando' version '3.21.2' runtime selector... +0ms
lando merged in additional config source from file 'C:\\snapshot\\cli\\config.yml' +30ms
lando merged in additional config source from file 'C:\\Users\\example\\.lando\\config.yml' +7ms
lando merged in additional config source from 'LANDO_*' envvars with data { installPath: 'C:\\Program Files\\Lando' } +5ms
lando final assembled minconf is {
lando configSources: [
lando 'C:\\snapshot\\cli\\config.yml',
lando 'C:\\Users\\example\\.lando\\config.yml'
lando ],
lando envPrefix: 'LANDO',
lando landoFile: '.lando.yml',
lando preLandoFiles: [
lando '.lando.base.yml',
lando '.lando.dist.yml',
lando '.lando.recipe.yml',
lando '.lando.upstream.yml'
lando ],
lando postLandoFiles: [ '.lando.local.yml', '.lando.user.yml' ],
lando runtime: 3,
lando srcRoot: 'C:\\snapshot\\cli',
lando userConfRoot: 'C:\\Users\\example\\.lando',
lando product: 'lando',
lando hyperdrive: 'hyperdrive',
lando channel: 'stable',
lando domain: 'ld',
lando mode: 'cli',
lando stats: [
lando { report: true, url: 'https://metrics.lando.dev' },
lando { report: false },
lando { url: 'https://metrics.devwithlando.io' }
lando ],
lando orchestratorBin: 'C:\\Program Files\\Docker\\Docker\\resources\\bin\\docker-compose',
lando installPath: 'C:\\Program Files\\Lando'
lando } +1ms
lando detected an app 'example' at 'C:\\dev\\lando\\exampled10' +32ms
lando using '@lando/core' runtime version 3 +1ms
lando starting lando with 'v3' runtime using cli { ENVPREFIX: undefined, LOGLEVELCONSOLE: 4, USERCONFROOT: undefined, COREBASE: '@lando/core' } +12ms
lando using cli config { args: [ '--dns-result-order=ipv4first' ], commit: false, coreBase: true, dev: false, entrypoint: 'C:/Users/example/.lando/bin/lando', file: 'C:\\Users\\example\\.lando\\bin\\lando.exe', installPath: 'C:\\Users\\example\\.lando\\bin', packaged: true, plugin: 'C:\\snapshot\\cli', slim: true, source: false } +1ms
lando using cli config { args: [ '--dns-result-order=ipv4first' ], commit: false, coreBase: true, dev: false, entrypoint: 'C:/Users/example/.lando/bin/lando', file: 'C:\\Users\\example\\.lando\\bin\\lando.exe', installPath: 'C:\\Users\\example\\.lando\\bin', packaged: true, plugin: 'C:\\snapshot\\cli', slim: true, source: false } +57ms
lando starting bootstrap at level APP... +2ms
lando config bootstrap beginning... +6ms
lando emitting event pre-bootstrap-config +1ms
lando plugin '@lando/core' loaded from C:\snapshot\cli\node_modules\@lando\core\index.js +26ms
lando plugin '@lando/healthcheck' loaded from C:/snapshot/cli/node_modules/@lando/core/plugins/healthcheck/index.js +4ms
lando plugin '@lando/networking' loaded from C:/snapshot/cli/node_modules/@lando/core/plugins/networking/index.js +2ms
lando plugin '@lando/proxy' loaded from C:/snapshot/cli/node_modules/@lando/core/plugins/proxy/index.js +3ms
lando plugin '@lando/scanner' loaded from C:/snapshot/cli/node_modules/@lando/core/plugins/scanner/index.js +2ms
lando plugin '@lando/sharing' loaded from C:/snapshot/cli/node_modules/@lando/core/plugins/sharing/index.js +1ms
lando removed duplicate plugin entries %o name=@lando/core, path=C:\snapshot\cli\node_modules\@lando\core, type=local +1ms
lando emitting event post-bootstrap-config +2ms
lando building proxy config... +1ms
lando config bootstrap completed. +3ms
lando tasks bootstrap beginning... +1ms
lando emitting event pre-bootstrap-tasks +0ms
lando autoloaded task config +25ms
lando autoloaded task destroy +1ms
lando autoloaded task info +0ms
lando autoloaded task init +5ms
lando autoloaded task list +2ms
lando autoloaded task logs +0ms
lando autoloaded task plugin-add +0ms
lando autoloaded task plugin-login +1ms
lando autoloaded task plugin-logout +0ms
lando autoloaded task plugin-remove +1ms
lando autoloaded task poweroff +0ms
lando autoloaded task rebuild +0ms
lando autoloaded task restart +1ms
lando autoloaded task setup +1ms
lando autoloaded task share +1ms
lando autoloaded task shellenv +0ms
lando autoloaded task ssh +0ms
lando autoloaded task start +1ms
lando autoloaded task stop +0ms
lando autoloaded task update +1ms
lando autoloaded task version +0ms
lando emitting event post-bootstrap-tasks +10ms
lando tasks bootstrap completed. +1ms
lando engine bootstrap beginning... +0ms
lando emitting event pre-bootstrap-engine +0ms
lando automoved scripts from C:\snapshot\cli\node_modules\@lando\core\scripts to C:\Users\example\.lando\scripts and set to mode 755 +335ms
lando automoved scripts from C:\snapshot\cli\node_modules\@lando\core\plugins\proxy\scripts to C:\Users\example\.lando\scripts and set to mode 755 +161ms
lando automoved scripts from C:\snapshot\cli\node_modules\@lando\core\plugins\sharing\scripts to C:\Users\example\.lando\scripts and set to mode 755 +152ms
lando emitting event post-bootstrap-engine +2ms
lando engine bootstrap completed. +1ms
lando app bootstrap beginning... +0ms
lando emitting event pre-bootstrap-app +0ms
lando autodiscovered legacy api 3 builder _appserver +3ms
lando autodiscovered legacy api 3 builder _casetup +0ms
lando autodiscovered legacy api 3 builder _init +1ms
lando autodiscovered legacy api 3 builder _lando +0ms
lando autodiscovered legacy api 3 builder _landoutil +0ms
lando autodiscovered legacy api 4 builder _service +0ms
lando autodiscovered legacy api 3 builder _service +0ms
lando autodiscovered legacy api 3 builder _webserver +0ms
lando autodiscovered legacy api 4 builder lando +0ms
lando autodiscovered legacy api 3 builder lando +1ms
lando autodiscovered legacy api 3 builder _proxy +0ms
lando autodiscovered legacy api 3 builder _mounter +0ms
lando emitting event post-bootstrap-app +0ms
lando app bootstrap completed. +5ms
lando bootstrap completed. +1ms
lando emitting event post-bootstrap +0ms
lando emitting event almost-ready +0ms
lando using docker-compose C:\Program Files\Docker\Docker\resources\bin\docker-compose.exe +1ms
lando checking docker version compatibility... +7ms
lando compatibility results name=compose, link=https://docs.docker.com/desktop/install/windows-install/, satisfied=true, untested=false, rupdate=true, wants=1.x.x || 2.x.x, tested=<=2.27.0, update=<=2.24.6, dockerVersion=true, version=1.29.2, name=desktop, link=https://docs.docker.com/desktop/install/windows-install/, satisfied=true, untested=false, rupdate=true, wants=>=4.0.0 <5, tested=<=4.30.0, update=<=4.28.0, dockerVersion=true, version=4.0.0 +1ms
lando emitting event ready +8ms
lando loading app example from config files 0=C:\dev\lando\exampled10\.lando.yml +8ms
lando app example has config name=example, recipe=drupal10, XXXXXXXXXXXXXXXX redacted XXXXXXXXXXXXXXXX +2ms
example initiatilizing app at C:\dev\lando\exampled10... +7ms
lando plugin '@lando/core' loaded from C:\snapshot\cli\node_modules\@lando\core\app.js +14ms
lando plugin '@lando/healthcheck' loaded from C:\snapshot\cli\node_modules\@lando\core\plugins\healthcheck\app.js +1ms
lando plugin '@lando/networking' loaded from C:\snapshot\cli\node_modules\@lando\core\plugins\networking\app.js +1ms
example proxy settings detected. +7ms
lando plugin '@lando/proxy' loaded from C:\snapshot\cli\node_modules\@lando\core\plugins\proxy\app.js +2ms
lando plugin '@lando/scanner' loaded from C:\snapshot\cli\node_modules\@lando\core\plugins\scanner\app.js +1ms
lando plugin '@lando/sharing' loaded from C:\snapshot\cli\node_modules\@lando\core\plugins\sharing\app.js +1ms
example emitting event pre-init +2ms
example WARN drupal10 is not a supported recipe type. +1ms
example building drupal10 recipe named +0ms
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
Error: Could not find a service builder called drupal10 in the builder registry!
at Factory.get (C:\snapshot\cli\node_modules\@lando\core\lib\factory.js)
at C:\snapshot\cli\node_modules\@lando\core\hooks\app-add-recipes.js
at AsyncEvents.<anonymous> (C:\snapshot\cli\node_modules\@lando\core\app.js)
From previous event:
at AsyncEvents.handle (C:\snapshot\cli\node_modules\@lando\core\lib\events.js)
at C:\snapshot\cli\node_modules\@lando\core\lib\events.js
at process.processImmediate (node:internal/timers:476:21)
From previous event:
at AsyncEvents.emit (C:\snapshot\cli\node_modules\@lando\core\lib\events.js)
at C:\snapshot\cli\node_modules\@lando\core\lib\app.js
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Node.js v18.19.1
Not sure if it could be related at all, but the 2nd step of the advanced installation instructions say to run Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser, however that's not allowed at my organization, so that command failed. I continued running .\setup-lando.ps1 -WSLOnly after that, though.
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): Y
Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the setting is overridden by
a policy defined at a more specific scope. Due to the override, your shell will retain its current effective
execution policy of RemoteSigned. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more
information please see "Get-Help Set-ExecutionPolicy".
At line:1 char:1
+ Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : PermissionDenied: (:) [Set-ExecutionPolicy], SecurityException
+ FullyQualifiedErrorId : ExecutionPolicyOverride,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand
Any ideas of what's going on here?