protonmail-bridge-docker icon indicating copy to clipboard operation
protonmail-bridge-docker copied to clipboard

Unraid cannot init

Open Hampo opened this issue 9 months ago • 5 comments
trafficstars

Followed the instructions in the Unraid community apps to run the following commands:

docker exec -it protonmail-bridge /bin/bash
chmod +x entrypoint.sh
./entrypoint.sh init

Received the error:

root@fe95c1bfa89d:/protonmail# chmod +x ./entrypoint.sh 
root@fe95c1bfa89d:/protonmail# ./entrypoint.sh init
+ [[ init == init ]]
+ gpg --generate-key --batch /protonmail/gpgparams
gpg: Generating a basic OpenPGP key
gpg: revocation certificate stored as '/root/.gnupg/openpgp-revocs.d/B1EA39DCE18CCD4AE92FF5FC0D96D02522FC35E8.rev'
gpg: done
+ pass init pass-key
Password store initialized for pass-key
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   4  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 4u
docker-credential-helpers/cHJvdG9ubWFpbC9icmlkZ2UtdjMvdXNlcnMvYnJpZGdlLXZhdWx0LWtleQ==/bridge-vault-key: reencrypting to 
+ protonmail-bridge --cli
WARN[Feb 16 21:57:17.466] Failed to create lock file; another instance is running

Hampo avatar Feb 16 '25 21:02 Hampo

can you run ps aux and report the output? you probably have a protonmail-bridge process running and need to use kill to end it. I'll get it fixed soon

simonfelding avatar Feb 17 '25 08:02 simonfelding

Sorry for the delay - after some further research I found that there's 2 processes that are running: bridge and protonmail-bridge. If you kill both, you can run the init command and go from there.

Hampo avatar Feb 17 '25 21:02 Hampo

Oh, and the output you wanted, ran on a fresh image:

USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.1  0.0   4068  2944 ?        Ss   21:04   0:00 bash /protonmail/entrypoint.sh
root           7  0.0  0.0  11064  3840 ?        S    21:04   0:00 socat TCP-LISTEN:25,fork TCP:127.0.0.1:1025
root           8  0.0  0.0  11064  3712 ?        S    21:04   0:00 socat TCP-LISTEN:143,fork TCP:127.0.0.1:1143
root          11  0.0  0.0   2588  1280 ?        S    21:04   0:00 cat faketty
root          12  0.0  0.0 1577132 10624 ?       Sl   21:04   0:00 protonmail-bridge --cli
root          18  0.5  0.0 2212452 33280 ?       Sl   21:04   0:00 /usr/lib/protonmail/bridge/bridge --cli --session-id 20250217_210438657 --launc
root          55  0.0  0.0  72544  3084 ?        Ss   21:04   0:00 gpg-agent --homedir /root/.gnupg --use-standard-socket --daemon
root          87  0.0  0.0   4332  3584 pts/0    Ss   21:04   0:00 bash
root          93  0.0  0.0   6352  3712 pts/0    R+   21:04   0:00 ps aux

Hampo avatar Feb 17 '25 21:02 Hampo

Can confirm, had two kill two processes with protonmail-bridge in their command before I could init.

danthi123 avatar Mar 12 '25 04:03 danthi123

that fixed it for me too on unraid

craigst avatar Apr 17 '25 12:04 craigst