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
ERROR: for index Cannot create container for service index: b'Mount denied:\nThe source path ... \nis not a valid Windows path' #1004
Comments
I'm hitting same problem. I also found that Docker did not start properly when installed as part of the Lando installation (it sat forever 'starting' leaving the Lando installer waiting), so I had to restart the PC and then docker started properly. I also had to manually go to Docker settings and share the c:\ drive. |
Hi @RichardDavies! Beta 46 included a Windows specific regression, we recommend rolling back to 45 and waiting for us to release 47 before upgrading again, sorry about that! |
… here until we have tests and better buildz
edit: @pirog Sorry, I assumed the issue would reopen, if I post a reply. Should I create a new issue?
|
@Markus-Schmitt this is already captured over at #1510 and only happens if you are using "excludes" which is currently an experimental and unsupported feature |
Bug Report
Tell us about your setup
Lando v3.0.0-beta.46 on Windows 10 Professional
Tell us about your
.lando.yml
Tell us about the command you were running
Tell us about the error you got
Tell us generally about your bug
After updating from beta 45 to beta 46, whenever I attempt to lando start or rebuild I get a handful of errors like
Please detail the steps we can take to replicate this bug. Be as detailed as possible.
git clone -c core.symlinks=true git@github.com:eGovPDX/portlandor.git git config core.autocrlf false lando start
Tell us more
Does this bug prevent you from using lando? Yes (at least beta 46)
I've tried (unsuccessfully) to fix this by uninstalling Lando and Docker, removing my ~/.lando directory, and reinstalling.
The text was updated successfully, but these errors were encountered: