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.001582
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 »

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.