Package Details: lando-bin 3.21.2-2

Git Clone URL: https://aur.archlinux.org/lando-bin.git (read-only, click to copy)
Package Base: lando-bin
Description: A free, open source, cross-platform, local development environment and DevOps tool built on Docker container technology
Upstream URL: https://docs.lando.dev/
Licenses: GPL
Conflicts: lando
Provides: lando
Submitter: dmp1ce
Maintainer: None
Last Packager: pfrenssen
Votes: 6
Popularity: 0.002476
First Submitted: 2021-06-17 20:04 (UTC)
Last Updated: 2024-09-16 09:59 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

GeoSot commented on 2021-10-14 09:41 (UTC)

You may try to use a function like below, that always return the latest (no-prebuild) tag, in order to get new releases on time

get_latest_release() { curl --silent "https://api.github.com/repos/lando/lando/releases/latest" | # Get latest release from GitHub api grep '"tag_name":' | # Get tag line sed -E 's/."([^"]+)"./\1/' # Pluck JSON value }

pkgver=get_latest_release

dmp1ce commented on 2021-10-01 21:02 (UTC)

I removed dependency on compose-switch.

dmp1ce commented on 2021-10-01 20:59 (UTC)

It appears docker-compose has a fix for the CLI not working as expected as well. I haven't tested for myself. https://github.com/docker/compose/issues/8698#issuecomment-931971665

dmp1ce commented on 2021-10-01 19:42 (UTC)

@zilvervos I'm not sure about that one. Maybe more changed with Docker Compose v2 than I thought. I would have thought it would just work.

I think the way the directory name is chosen for v2 changed which is why it cannot find your containers. If you started a new project with v2 it might work.

I'm just trying to find information on this because it is new to me. https://www.cloudsavvyit.com/12144/whats-new-in-docker-compose-v2/

zilvervos commented on 2021-10-01 19:02 (UTC) (edited on 2021-10-01 19:02 (UTC) by zilvervos)

I was too quick with concluding that my problem was solved. With the new symlink + the latest version of docker, docker-compose and compose-switch lando starts up, but generates another error: ERROR ==> Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1

No clue what this could be...

Again: with downgraded docker and docker-compose I could launch my development environment earlier today.

zilvervos commented on 2021-10-01 12:30 (UTC) (edited on 2021-10-01 12:35 (UTC) by zilvervos)

Ah yes, that does the job! Thanks a lot for your help and attention to my problem.

dmp1ce commented on 2021-10-01 12:16 (UTC)

I had my symlink command wrong. Getting the correct symlink to compose-switch should work to get lando working. It seemed to work for me as a temporary solution.

# ln -s /usr/bin/compose-switch /usr/local/bin/docker-compose

If which docker-compose resolves then it should work for lando too.

zilvervos commented on 2021-10-01 11:29 (UTC) (edited on 2021-10-01 12:08 (UTC) by zilvervos)

In the meantime I have downgraded to earlier versions of docker and docker-compose and everything works fine again. I'll keep an eye on when lando has fixed the issue.

Tbaile commented on 2021-10-01 11:18 (UTC)

As of docker-compose v2.0.1, compose-switch is not needed anymore. They added the possibility to run the docker plugin as standalone, allowing lando to fetch the correct binary of compose. As of now, a Github issue has been opened, since lando doesn't fully support composer V2.

zilvervos commented on 2021-10-01 10:51 (UTC)

Created the symlink, but it doesn't help. Still the same error message when launching lando start from the app (website development environment) directory.

On my system compose switch is located here: [erik@celaeno]$ pacman -Ql compose-switch compose-switch /usr/ compose-switch /usr/bin/ compose-switch /usr/bin/compose-switch

No idea where the lando script would look for an instance of docker-compose.

« First ‹ Previous 1 2 3 4 Next › Last »