Closed uberhacker closed 1 year ago
Ah-ha! The issue appears to be docker-compose. If I downgrade to 1.29.2, it fixes this issue. See https://github.com/lando/cli/pull/151, although that PR needs to be refactored for the latest Lando code.
In any event, Lando v3.8.1 is not compatible with docker-compose 2.15.0.
@uberhacker makes sense as we don't support docker compose v2.
we've started to work on the new V4 runtime over at https://github.com/lando/core-next which will also only support docker compose V1 at first release. however v4 moves lando to more of a "component/registry" design so all "components" will be swappable globally and on a per app basis.
this means that it will be MUCH easier and less scary for us (or anyone for that matter) to provide alternate "orchestrators" eg docker compose v2 or kubernetes.
This issue appears to be consistent across different projects using various recipes and independent of whether docker is running inside the Linux distro (tested with Ubuntu 20.04) or whether Docker Desktop is running the docker services. I don't know what else to say other than try it out yourself to see if the issue is repeatable. Example output from a project using the Pantheon recipe shown below:
Output from
.lando.yml
below:Device specs below:
Windows specs below:
WSL2 specs below:
Possible causes:
I found it odd that
No such container: landoproxyhyperion5000gandalfedition_proxy_1
reported underscores but the container name reported by docker had dashes as shown below:Let me know if any more info is needed. Thanks for looking.