summaryrefslogtreecommitdiff
path: root/frontends
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-06-19 22:06:35 +0300
committerPaul Buetow <paul@buetow.org>2026-06-19 22:06:35 +0300
commitf4988baeeb975ff33a1d62b01e0cda17c7da9c7e (patch)
tree0921b63f05f01ac3d8ec971150e323809d9cc3c8 /frontends
parent01e99ef089e3a2370acf554f5ba8cb90f3c0a2bb (diff)
protonbridge: use init container for GPG+pass setup; fix TTY+home issues
Root causes of prior CrashLoopBackOff: 1. %no-passphrase unsupported; %no-protection needed instead 2. GPG agent couldn't use pinentry without a TTY 3. Container runs as root (HOME=/root) so mounting at /home/protonmail was wrong Fix: dedicated setup-pass init container (shares image, has gpg+pass) that configures allow-loopback-pinentry in gpg-agent.conf + gpg.conf, then generates a passphrase-free key and inits the pass store. All state is written to /bridge-data (PVC mount), with GNUPGHOME and PASSWORD_STORE_DIR env vars so the main container finds the store. Main container no longer overrides the default entrypoint. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Diffstat (limited to 'frontends')
0 files changed, 0 insertions, 0 deletions