Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container always fails to start #85

Open
CodePhase opened this issue Apr 14, 2023 · 3 comments
Open

Container always fails to start #85

CodePhase opened this issue Apr 14, 2023 · 3 comments

Comments

@CodePhase
Copy link

I am attempting to run this container on a RHEL 8 host using podman. I have used it in the past on the same type of system but, due to a system failure I lost that host. I am trying to get this container working on another host with a similar configuration. Unfortunately I have no idea what version I had running in the past.

I have tried multiple versions of the container and they all fail to start. I have tried running them with and without the 'init' argument to set up the environment. I get this error with 'latest':

sudo podman run -it --rm --name protonmail --network protonmail-20 --mount type=bind,source=/var/local/protonmail-bridge,target=/root --security-opt label=disable shenxn/protonmail-bridge:latest
+ [[ '' == init ]]
+ rm -f faketty
+ socat TCP-LISTEN:25,fork TCP:127.0.0.1:1025
+ socat TCP-LISTEN:143,fork TCP:127.0.0.1:1143
+ mkfifo faketty
+ cat faketty
+ protonmail-bridge --cli
WARN[0000] Failed to add test credentials to keychain    error="failed to open dbus connection: exec: \"dbus-launch\": executable file not found in $PATH" helper="*keychain.SecretServiceDBusHelper"
INFO[0006] Migrating keychain helper                    
FATA[Apr 14 01:42:18.114] another instance is already running but it could not be raised 
FATA[Apr 14 01:42:18.117] Failed to launch                              error="exit status 1" exe_path=/usr/lib/protonmail/bridge/bridge exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.0.21

I get a different error with the 'init' argument. I've also seen a suggestion to try version 2.4.8-1:

sudo podman run -it --rm --name protonmail --network protonmail-20 --mount type=bind,source=/var/local/protonmail-bridge,target=/root --security-opt lab=disable shenxn/protonmail-bridge:2.4.8-1
+ [[ '' == init ]]
+ rm -f faketty
+ socat TCP-LISTEN:25,fork TCP:127.0.0.1:1025
+ socat TCP-LISTEN:143,fork TCP:127.0.0.1:1143
+ mkfifo faketty
+ cat faketty
+ protonmail-bridge --cli
INFO[Apr 14 01:43:35.162] No more updates found, looking up bridge executable  error="no available newer versions" exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=2.4.8
WARN[0000] Failed to add test credentials to keychain    error="failed to open dbus connection: exec: \"dbus-launch\": executable file not found in $PATH" helper="*keychain.SecretServiceDBusHelper"
WARN[Apr 14 01:43:41.647] Cannot load preferences file, creating new one  error="open /root/.config/protonmail/bridge/prefs.json: no such file or directory"
WARN[Apr 14 01:43:47.969] Proton Mail Bridge is already running         error="Version string empty"
FATA[Apr 14 01:43:47.970] Failed to create app base                     error="Get \"http://127.0.0.1:1042/focus\": dial tcp 127.0.0.1:1042: connect: connection refused"
FATA[Apr 14 01:43:47.972] Failed to launch                              error="exit status 1" exe_path=/usr/lib/protonmail/bridge/bridge exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=2.4.8

Running this version with 'init' fails with a similar error:

sudo podman run -it --rm --name protonmail --network protonmail-20 --mount type=bind,source=/var/local/protonmail-bridge,target=/root --security-opt label=disable shenxn/protonmail-bridge:2.4.8-1 init
+ [[ 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 854B3F167C50FA14 marked as ultimately trusted
gpg: directory '/root/.gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/root/.gnupg/openpgp-revocs.d/6BBDD89E53376076236510ED854B3F167C50FA14.rev'
gpg: done
+ pass init pass-key
mkdir: created directory '/root/.password-store/'
Password store initialized for pass-key
+ protonmail-bridge --cli
INFO[Apr 14 01:46:09.814] No more updates found, looking up bridge executable  error="no available newer versions" exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=2.4.8
WARN[0000] Failed to add test credentials to keychain    error="failed to open dbus connection: exec: \"dbus-launch\": executable file not found in $PATH" helper="*keychain.SecretServiceDBusHelper"
WARN[Apr 14 01:46:16.251] Cannot load preferences file, creating new one  error="open /root/.config/protonmail/bridge/prefs.json: no such file or directory"
WARN[Apr 14 01:46:22.597] Proton Mail Bridge is already running         error="Version string empty"
FATA[Apr 14 01:46:22.598] Failed to create app base                     error="Get \"http://127.0.0.1:1042/focus\": dial tcp 127.0.0.1:1042: connect: connection refused"
FATA[Apr 14 01:46:22.601] Failed to launch                              error="exit status 1" exe_path=/usr/lib/protonmail/bridge/bridge exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=2.4.8

I have tried launching the container and having a bash prompt. When I run the commands manuall (entrypoint.sh and also protonmail-bridge --cli) I get the same results. I have tried running those commands and checking 'top' when they fail and there is no instance of protonmail running. I have seen the advice to kill a rogue instance of it but none exists.

I'm sure it's got to be a problem with my host. Has anyone else been seeing this? Anything I could try to get it working again?

@AviationAce
Copy link

I am absolutely seeing the SAME thing.
I'm trying to run this container with Ubuntu running as a VM under Proxmox.
Is there anything we can do to help each other track the problem down?

@Wmartin417
Copy link

Exact same problem here, I've tried everything I could so far, but no dice..

@assemnabill
Copy link

Same problem here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants