Unable to start container in CLI mode

[ckhyatt]

I need to make a configuration change but I am unable to start in CLi mode. I stop the container run the command below to run in interactive mode. I receive the following error.

docker run --rm -it -v protonmail:/root shenxn/protonmail-bridge init

/root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge: error while loading shared libraries: libfido2.so.1: cannot open shared object file: No such file or directory
FATA[Mar 11 18:10:37.124] Failed to launch error="exit status 127" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/bridge exe_to_launch=bridge launcher_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_version=3.22.0
FATA[Mar 11 18:10:37.125] Failed to launch error="exit status 1" exe_path=/root/.local/share/protonmail/bridge-v3/updates/3.22.0/proton-bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.19.0

[Neriderc]

No one has heard from the maintainer for a while, but this seems to be the same error as reported in #141 and #135
.

There's an LLM generated fix in a fork linked in that issue if you trust it.

[miguelccoelho]

An alternative is to manually install the several libraries missing, from inside the container. You can use apt-get install for that.

[Neriderc]

An alternative is to manually install the several libraries missing, from inside the container. You can use apt-get install for that.

This worked for me! Specifically, installing libfido2-1.

For more specific instructions:

1. Go into the container. This might be with compose or not.

With compose:
sudo docker compose exec -it <service name> bash

Without compose:
sudo docker exec -it <container name> bash

2. Then run the installation command:
   apt-get update && apt-get install -y libfido2-1

Then restart the container (don't use down as this will reset the container and you'll lose the newly installed package):
Compose:
sudo docker compose restart
Not compose:
sudo docker restart <container name>

Note that the container logs are not cleared on a restart, so you'll still see the errors from before if you check logs, but you should also see a message that the sync was successful.

[miguelccoelho]

I should've kept a list of all the libraries I had to install, for me, they were quite a few. In any case, that's pretty much what I did. In my case, it was:

1. update a library
2. try to start the bridge
3. check the library that failed
4. go back to 1 until the bridge starts

[Neriderc]

Interesting! That libfido2-1 package was the only thing I had to install to get the container to start up ok.

[geransmith]

For me, the fix here worked: #147 (comment)

No other installs needed.

[PaulKierstead]

I made a fork which fixes the dependency, also adds pkill if you need that (I do for kubernetes) and also fixed pkill to use -f, as the process name exceeded the max length (15 characters)

https://github.com/PaulKierstead/protonmail-bridge-docker