"Failed to launch" on Raspberry Pi 4 (arm64)

[Zettergaard]

Getting the following output when running the docker command with the latest build version.

root@atlas:~# docker run --rm -it -v protonmail:/root shenxn/protonmail-bridge:build init
+ [[ init == init ]]
+ gpg --generate-key --batch /protonmail/gpgparams
gpg: Generating a basic OpenPGP key
gpg: key E8D639E605C8C3F9 marked as ultimately trusted
gpg: revocation certificate stored as '/root/.gnupg/openpgp-revocs.d/B2D0D63D72BEC9E89AFDE13CE8D639E605C8C3F9.rev'
gpg: done
+ pass init pass-key
Password store initialized for pass-key
+ pkill protonmail-bridge
+ true
+ /protonmail/proton-bridge --cli init
INFO[Jan 18 08:36:31.541] No more updates found, looking up bridge executable  error="no available newer versions" exe_to_launch=bridge launcher_path=/protonmail/proton-bridge launcher_version=2.4.8+git
/protonmail/bridge: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /protonmail/bridge)
/protonmail/bridge: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /protonmail/bridge)
FATA[Jan 18 08:36:31.546] Failed to launch                              error="exit status 1" exe_path=/protonmail/bridge exe_to_launch=bridge launcher_path=/protonmail/proton-bridge launcher_version=2.4.8+git

Running with version 2.4.0-build, works though.

Operating system:

root@atlas:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

Anything I am missing?

Cheers

[IngwiePhoenix]

Same here on a Rockchip SOC:

root@FriendlyWrt /s/s/proton-bridge# docker-compose run bridge init
[+] Running 1/0
 ⠿ Network proton-bridge_default  Created                                                                                                                                              0.0s
+ [[ init == init ]]
+ gpg --generate-key --batch /protonmail/gpgparams
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: Generating a basic OpenPGP key
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key 1426CCDFE0A76307 marked as ultimately trusted
gpg: directory '/root/.gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/root/.gnupg/openpgp-revocs.d/CBF5DACAF50925FC135E06C41426CCDFE0A76307.rev'
gpg: done
+ pass init pass-key
mkdir: created directory '/root/.password-store/'
Password store initialized for pass-key
+ pkill protonmail-bridge
+ true
+ /protonmail/proton-bridge --cli init
INFO[Jan 19 10:10:43.962] No more updates found, looking up bridge executable  error="no available newer versions" exe_to_launch=bridge launcher_path=/protonmail/proton-bridge launcher_version=2.4.8+git
/protonmail/bridge: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /protonmail/bridge)
/protonmail/bridge: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /protonmail/bridge)
FATA[Jan 19 10:10:43.966] Failed to launch                              error="exit status 1" exe_path=/protonmail/bridge exe_to_launch=bridge launcher_path=/protonmail/proton-bridge launcher_version=2.4.8+git

Device is a FriendlyElec NanoPi R6s. It's a arm64 SBC.

Thanks!

[Robb-Fr]

Same error on MacOS M1 chip with the build aarch64 image

❯ docker run --rm -it -v protonmail:/root shenxn/protonmail-bridge:build init
+ [[ init == init ]]
+ gpg --generate-key --batch /protonmail/gpgparams
gpg: Generating a basic OpenPGP key
gpg: key 268C3B113AD506BA marked as ultimately trusted
gpg: revocation certificate stored as '/root/.gnupg/openpgp-revocs.d/F1F2058CC9050E8E91837591268C3B113AD506BA.rev'
gpg: done
+ pass init pass-key
Password store initialized for pass-key
+ pkill protonmail-bridge
+ true
+ /protonmail/proton-bridge --cli init
INFO[Jan 21 20:47:43.939] No more updates found, looking up bridge executable  error="no available newer versions" exe_to_launch=bridge launcher_path=/protonmail/proton-bridge launcher_version=2.4.8+git
/protonmail/bridge: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /protonmail/bridge)
/protonmail/bridge: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /protonmail/bridge)
FATA[Jan 21 20:47:43.940] Failed to launch                              error="exit status 1" exe_path=/protonmail/bridge exe_to_launch=bridge launcher_path=/protonmail/proton-bridge launcher_version=2.4.8+git

[schklom]

In the meantime, try using shenxn/protonmail-bridge:2.4.0-build, it works for me for some reason.

[Lolen10]

This issue is still present but I have a workaround for you. With this you can execute the amd64-image on the raspberry pi (arm64).

Firstly run this: docker run --privileged --rm tonistiigi/binfmt --install amd64 This will configure the host to be able to run amd64 containers.

Next download the amd64 image: docker pull --platform=amd64 shenxn/protonmail-bridge:latest The --platform parameter defines the platform this image should be. In this case amd64. If you leave it out you get the error "no matching manifest for linux/arm64/v8 in the manifest list entries" because it tries to download the arm64 version which doesn't exist in the latest-tag.

The last command to run is: docker run -d --name=protonmail-bridge -v protonmail:/root -p 1025:25/tcp -p 1143:143/tcp --restart=unless-stopped --platform=amd64 shenxn/protonmail-bridge If you have customized your installation, change this to your needs. The only important part is the --platform parameter (again). This way it worked for me like a charm.

If you use portainer: You can't update it within portainer. It just doesn't work. For this you need to run the last 2 commands again.

If you don't need this anymore, you can uninstall it with: docker run --privileged --rm tonistiigi/binfmt --uninstall amd64

[schklom]

@Lolen10 How much CPU and RAM does a container running that image consume compared to the one made for arm64? I am wondering if using QEMU is very taxing or just barely.

[Lolen10]

@schklom I don't use this anymore, as it (somehow) doesn't work on my new Raspberry Pi 5 anymore (I migrated to RPi 5). When I used it on my RPi 4 back then it worked just fine. But now to your question.

My old RPi 4 had 1GB RAM and it was running along with some other containers. So I guess the RAM and CPU usage wasn't that high. But might be a bit higher than native.