Package Details: lando-bin 3.6.4-1

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: pfrenssen
Last Packager: dmp1ce
Votes: 2
Popularity: 0.003010
First Submitted: 2021-06-17 20:04 (UTC)
Last Updated: 2022-05-07 16:25 (UTC)

Latest Comments

dmp1ce commented on 2022-04-04 11:27 (UTC)

Thanks. I found the issue here. I'll update the project with libxcrypt-compat dependency.

https://github.com/lando/lando/issues/3326

TwoD commented on 2022-04-03 18:42 (UTC)

@dmp1ce I got it when running lando start. libxcrypt-compat also solved it for me.

dmp1ce commented on 2022-02-24 01:37 (UTC)

@pfrenssen When do you get this error?

pfrenssen commented on 2022-02-23 21:39 (UTC)

I am seeing the following error (possibly after updating the glibc package to the latest version):

Error loading Python lib '/tmp/_MEItnE8v0/libpython3.7m.so.1.0': dlopen: libcrypt.so.1: cannot open shared object file

This can be solved by installing the libxcrypt-compat package from the AUR.

dmp1ce commented on 2022-02-12 10:30 (UTC)

I returned the docker-compose binary. Thanks for letting me know it is still needed.

pfrenssen commented on 2022-01-19 21:12 (UTC)

Another confirmation that the workaround of @mpolishchuck works. Can we update the PKGBUILD to no longer remove the docker-compose that ships with Lando?

Gugols commented on 2022-01-16 19:06 (UTC)

There are .pacman packages available @ https://github.com/lando/lando/releases for the latest stable releases. v3.6.0 works just fine for me.

madjoe commented on 2022-01-09 12:15 (UTC)

Sadly, this is the only version that works for me, thanks to @mpolishchuck. Currently lando and lando-git are broken.

mpolishchuck commented on 2022-01-08 22:34 (UTC)

I think removing "extra copy of docker-compose" was bad idea.

Lando ships docker-compose version 1 (or it is compose-switch, I did not dig so deep). Since the latest version of docker-compose in community repository is 2.2.3 (at the moment) lando cannot work with it. Proof: https://github.com/lando/cli/issues/46#issuecomment-932454887. So docker-compose from lando package works. I've removed the following lines:

    # Don't need extra copy of docker-compose
    rm "${pkgdir}/usr/share/lando/bin/docker-compose"

And now lando works on my machine (Docker 20.10.12, Docker Compose 2.2.3).

Fidelix commented on 2021-12-25 15:08 (UTC) (edited on 2021-12-25 15:08 (UTC) by Fidelix)

Unfortunately this package is broken for me, I think due to the issue mentioned by Gregg.

Downgrading docker-compose and/or python (to 3.9) did not work.

However, downloading the .pacman file straight from the lando releases worked fine.

ElijahLynn commented on 2021-12-16 19:48 (UTC) (edited on 2021-12-16 19:49 (UTC) by ElijahLynn)

We opened an issue for GreggHendrix's issue here https://github.com/lando/lando/issues/3255 and it appears the issue is that docker-compose got updated to a 2.x version and we downgraded to a 1.29.2 version to get it working, it has to do with underscores vs hyphens.

If this is happening to anyone else, do a:

  1. ls /var/cache/pacman/pkg/ | grep docker-compose # Look for the latest 1.x version
  2. pacman --upgrade /var/cache/pacman/pkg/docker-compose-1.29.2-1-any.pkg.tar.zst # your version may be different
  3. Then edit /etc/pacman.conf and add IgnorePkg = docker-compose.

GreggHendrix commented on 2021-12-16 17:46 (UTC)

I knew that I shouldnt have installed the new version of lando...I just got SO excited by everyone updating! Does anyone have any insight on this error?

After running lando start I got this :

ERROR ==> Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1 message=Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1 , stack=Error: Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1 at /snapshot/cli/lib/docker.js at processImmediate (internal/timers.js:464:21) From previous event: at containerOpt (/snapshot/cli/lib/docker.js) at Landerode.scan (/snapshot/cli/lib/docker.js) at Object.scan (/snapshot/cli/lib/router.js) at run (/snapshot/cli/lib/engine.js) at /snapshot/cli/lib/router.js From previous event: at Object.eventWrapper (/snapshot/cli/lib/router.js) at Engine.engineCmd (/snapshot/cli/lib/engine.js) at Engine.scan (/snapshot/cli/lib/engine.js) at /snapshot/cli/plugins/lando-networking/app.js From previous event: at AsyncEvents.<anonymous> (/snapshot/cli/plugins/lando-networking/app.js) at AsyncEvents.handle (/snapshot/cli/lib/events.js) at /snapshot/cli/lib/events.js at processImmediate (internal/timers.js:464:21) From previous event: at AsyncEvents.emit (/snapshot/cli/lib/events.js) at /snapshot/cli/lib/app.js From previous event: at App.start (/snapshot/cli/lib/app.js) at Object.run (/snapshot/cli/plugins/lando-core/tasks/start.js) at /snapshot/cli/lib/cli.js at processImmediate (internal/timers.js:464:21) From previous event: at /snapshot/cli/lib/cli.js From previous event: at Object.handler (/snapshot/cli/lib/cli.js) at Object.runCommand (/snapshot/cli/node_modules/yargs/lib/command.js:238:44) at Object.parseArgs [as _parseArgs] (/snapshot/cli/node_modules/yargs/yargs.js:1063:30) at Function.get [as argv] (/snapshot/cli/node_modules/yargs/yargs.js:1004:21) at Cli.init (/snapshot/cli/lib/cli.js) at Cli.run (/snapshot/cli/lib/cli.js) at Object.<anonymous> (/snapshot/cli/bin/lando.js) at Module._compile (pkg/prelude/bootstrap.js:1751:22) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:14) at Function.runMain (pkg/prelude/bootstrap.js:1804:12) at internal/main/run_main_module.js:17:47, stackCleaned=true

I then ran lando rebuild and got this error :

ERROR ==> database reported as unhealthy. ERROR ==> Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1

I'm SUPER out of my depth with lando in general (haha). I'm thinking that since I don't really know what I'm doing...Perhaps the best thing for me is to uninstall and re-install the previous version that was working? Any thoughts would be appreciated

dmp1ce commented on 2021-10-14 10:19 (UTC)

I'm not going to do that @GeoSot because I want each release to be fixed to a version and not change for any reason.

However, you could create a rolling release with your method using pkgver() to set the pkgver. See lando-git for an example. You'll need to get the checksum for the .deb dynamically too though.

It is too bad lando-git is broken because that one would get the latest version every time, if it worked.

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.

dmp1ce commented on 2021-09-30 21:32 (UTC) (edited on 2021-10-01 12:11 (UTC) by dmp1ce)

I assumed it would work but I didn't test myself.

Try creating a symlink to compose-switch.

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

I asked the maintainer of compose-switch to just install "docker-compose" instead of "compose-switch" so scripts will work as before.

zilvervos commented on 2021-09-30 19:50 (UTC) (edited on 2021-09-30 19:52 (UTC) by zilvervos)

Thanks for the quick action! The update has been applied on my system, but I still get the same error. I use lando as a tool for developing websites and it worked fine for me until today. I know next to nothing about docker and compose. A few weeks ago I could launch the development environment by issuing the command 'lando start' in the development environment directory.

Do I need to perform some command line action with compose-switch?

dmp1ce commented on 2021-09-30 12:29 (UTC)

I added compose-switch as a dependency until lando fixes the issue upstream.

dmp1ce commented on 2021-09-30 12:14 (UTC)

There is a package for compose-switch as well. https://aur.archlinux.org/packages/compose-switch/

dmp1ce commented on 2021-09-30 12:13 (UTC)

It looks like someone already did. https://github.com/lando/lando/issues/3075#issuecomment-929973099

dmp1ce commented on 2021-09-30 12:11 (UTC) (edited on 2021-09-30 12:12 (UTC) by dmp1ce)

@zilvervos, Perhaps try compose-switch here: https://github.com/docker/compose-switch

I'll create an issue with the upstream lando project.

zilvervos commented on 2021-09-30 09:20 (UTC)

Hello. I didn't use lando for the past few weeks and today when I tried to start a lando app I got an unexpected error message: "Lando could not detect an installation of docker-compose, which is a required dependency!"

I did some research and fount the following thread (posted yesterday) on the Arch Linux Forum: https://bbs.archlinux.org/viewtopic.php?id=269997

I read there that in the most recent version of docker, the docker-compose command no longer exists, but that compose is now is a subcommand of docker.

I guess this is causing the error generated by lando-bin.

neeks commented on 2021-06-28 23:42 (UTC) (edited on 2021-06-28 23:43 (UTC) by neeks)

Could you add the following to the PKGBUILD:

conflicts=("lando")
provides=("lando")