Get error on commands on service appserver

radicle
1

I use Radicle with Lando and everything was working fine until yesterday. However, now I am unable to execute any commands on the appserver service. When I try to run commands such as “lando login,” “lando acorn,” or “lando flush,” I receive the error message “Segmentation fault.”

I have attempted to fix the issue by increasing Docker memory and swap, as well as removing everything with the command “lando poweroff && docker system prune -a --volumes && rm -rf ~/.lando/cache.” (Command found here: Purge all Docker Containers & Lando Cache · GitHub)

For your information, I am using a MacBook with an Arm M1 Pro.
The appservice container is using Rosetta to emulate amd64.

Does anyone have any suggestions on how to resolve this issue?

Thank you in advance.

2

I have now removed Lando and Docker and reinstalled both.

However, I am still getting the same error:

➜  project git:(main) ✗ ld login
./composer.json has been created
Running composer update aaemnnosttv/wp-cli-login-command
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Lock file operations: 2 installs, 0 updates, 0 removals
  - Locking aaemnnosttv/wp-cli-login-command (dev-master 272effd)
  - Locking composer/semver (3.3.2)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 2 installs, 0 updates, 0 removals
  - Downloading composer/semver (3.3.2)
  - Downloading aaemnnosttv/wp-cli-login-command (dev-master 272effd)
  - Installing composer/semver (3.3.2): Extracting archive
  - Installing aaemnnosttv/wp-cli-login-command (dev-master 272effd): Extracting archive
Generating autoload files
1 package you are using is looking for funding.
Use the `composer fund` command to find out more!
Segmentation fault
Segmentation fault
Segmentation fault
3

Unfortunately I think this is quite a complex issue. There are recent reports of Docker’s Rosetta integration causing segfaults.

Docker officially says:

In summary, running Intel-based containers on Arm-based machines should be regarded as “best effort” only. We recommend running arm64 containers on Apple silicon machines whenever possible, and encouraging container authors to produce arm64, or multi-arch, versions of their containers.

Lando also say similar:

Note that Apple Silicon support is still a work in progress and YMMV.

A sure-fire solution would be to run native ARM containers. Is that possible with your setup? This Lando issue may help you.