proton_nextcloud_podman/protonmail-bridge-nextcoud-podman
1
0
Fork 0
forked from Mouws/protonmail-bridge-nextcoud-podman
Code Pull Requests Activity

Fix entrypoint so it works correctly on init

Browse Source 
Ran into this issue when trying to use in kubernetes via k8s-at-home/protonmail-bridge. Took a bit of figuring out before I realized I had to manually kill the other instance. The only output from the failed load is a dbus issue, and an immediate exit.
This commit is contained in:
Nilesh 2022-05-12 11:31:03 -07:00 committed by GitHub
parent 86e10823e0
commit 680e82076e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
build/entrypoint.sh
View File

@ -8,6 +8,9 @@ if [[ $1 == init ]]; then
# Initialize pass # Initialize pass
gpg --generate-key --batch /protonmail/gpgparams gpg --generate-key --batch /protonmail/gpgparams
pass init pass-key pass init pass-key
# Kill the other instance as only one can be running at a time
pkill protonmail-bridge
# Login # Login
/protonmail/proton-bridge --cli $@ /protonmail/proton-bridge --cli $@