Error: Could not find a service builder called drupal10 in the builder registry! #49
Labels
bug
Something isn't working
Comments
|
Oh... it seems that I need to run
|
|
Hmm well it installed all the plugins, but still needs docker-compose, but that throws a "socket hang up" error.
Here's the relevant output from |
|
I restarted my computer and now it thinks my user isn't already part of the docker-users group, but before I restarted it said this was already "Dialed". I confirmed in my Computer Management > System Tools > Local Users and Groups > Groups that the user account it's trying to add is already in the docker-users group. I don't know why lando setup thinks it's not.
|
|
It seems like the initial install didn't succeed and left things in a broken state. You linked to the advanced instructions, which say to adapt the example to your needs. Can you say what adaptations you made? The logs show that lando thinks it should be installing things in the profile of a user named "example" which would cause a lot of problems if that's not your username. Could be the result of some incorrect parameters during the install. You might want to delete the ".lando" directory from your C:\Users\YOURNAME directory, if it exists, then reinstall Lando with the defaults to make sure it wasn't an issue with the advanced install parameters. |
|
Hey sure, the adaptations I made for the advanced instructions were to run it with the I did a find/replace on my real username with "example" before pasting that output here. On the 2nd step of the advanced installation instructions it says to run |
|
The execution policy is a system policy that is effective regardless of whether you're an admin. It has you run that command to change the policy because Windows doesn't allow you to run scripts at all by default. If the script did run for you, the more specific policy set by your org was to allow the script which means you can ignore that error. The reason you don't need to do this when using the one-liner is that the commands used there are streaming the downloaded text into the execution environment rather than saving and then running a script file. Since there's no actual script saved on the computer, Windows behaves as though you're typing the lines of the script into powershell yourself. You mentioned that you ran this in an elevated prompt. I think that may have caused some issues because most of the installation needs to occur in your non-elevated profile. It really only needs the elevation to install Docker and an elevated prompt may have caused some things such as docker-compose to be installed in a non-shared admin user space instead of your own. I would remove the |
|
Interesting! I appreciate the explanation! I just assumed it needed to be ran from PowerShell with admin privileges because my organization requires that in order to install anything. For example, the legacy Lando EXE installer had to be ran with admin privileges for my non-admin user account to run I ran the PowerShell installer script I'll try the suggestions you mentioned about removing the |
|
It's also worth noting that if the only WSL instances on your machine are the ones created by Docker Desktop, then there's no need to run the install script with the -NoWSL because the script skips those distros anyway. It won't do anything in WSL if there are no other active distros. |
|
Good info. I do happen to have one other Ubuntu distro installed, so it tries to use that and I'm supposed to prevent it from doing that, to abide by my organization's security policy. I'm curious about the reason why it thought my
Before wiping out my Is Also, this seems like a dumb question, but how do I uninstall this new version of Lando? It's not listed in my Windows Control Panel > Programs and Features. |
|
I removed the
|
|
It's no longer installed as a traditional Windows application since it really isn't one. You can delete the Lando will download and use its own version of docker-compose into Does it succeed if you run |
|
I re-ran Then it got to this point and prompted me for UAC elevation to add my username to the
Debug logs after that point: |
|
The "socket hang up" error seems like it's not using my Windows HTTP_PROXY and HTTPS_PROXY environment variable settings in C:\snapshot\cli\node_modules\@lando\core\node_modules\axios\dist\node\axios.cjs |
|
For the UAC prompt, you'll need to enter credentials for a user that has permissions to edit local user roles. Probably an admin. |
|
My username was already added to the
I'm able to download https://github.com/docker/compose/releases/download/v2.27.0/docker-compose-windows-x86_64.exe using curl in PowerShell. So I'm not sure what's causing the "socket hang up" error
|
|
My system admin granted my user account admin privileges and it still failed to add my user to the
Debug logs: |
|
After that
Is there any reason why |
|
Trying to press onward, I made sure my I assume this is okay? I don't know if there are any further steps that need to happen in I went ahead and ran That part of my |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
drupal10recipe that has worked flawlessly on v3.20.4.After updating Lando to v3.21.2, I ran
lando destroyto remove everything and then ranlando rebuild, but I get this error:I ran
lando updatefor the first time and got this:I ran
lando setupand got this:I ran
lando update --debugand now I get this: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 -WSLOnlyafter that, though.Any ideas of what's going on here?
The text was updated successfully, but these errors were encountered: