-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Cannot start any project in 3.21.0-beta.1 #121
Labels
Comments
@eldair can you share your landofile so we can try to replicate? |
@pirog sure, it happens in any app, here are two lando files
this is
second lando file:
|
@pirog Is this issue fixed in latest update(s)? PHP 8.3 is unusable without v3.21 |
@pirog It seems to be fixed now, I will close the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have updated lando to the latest version today and am unable to start any project - here is the error message
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/fbca942db8f70dc7d5150f9e042d5580d249ce84d490da08534929fbb15e1870" to rootfs at "/opt/bitnami/nginx/conf/lando.conf": mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/fbca942db8f70dc7d5150f9e042d5580d249ce84d490da08534929fbb15e1870:/opt/bitnami/nginx/conf/lando.conf (via /proc/self/fd/6), flags: 0x5000: no such file or directory: unknown
Lando is installed in wsl (2) not in windows directly, docker version is 4.27.2.
If I run lando destroy and then lando start, it works - but if I run lando start on a stopped project it throws the error above.
Also, if I restart docker and start container via docker ui it will start but if I try lando start (which fails) then it becomes impossible to start it again via docker ui - restarting docker will again allows me to start containers via docker ui.
The text was updated successfully, but these errors were encountered: