Docker/protonmail-bridge
1
0
Fork 0
Code Issues Actions 1 Packages Activity

fix: force patched nogui bridge binary to bind on 0.0.0.0
Build and Push Docker Container / build-and-push (push) Successful in 7m1s
Details

Browse Source 
- Install patched nogui bridge as both /usr/bin/bridge and /usr/bin/proton-bridge

- Give copied binaries explicit target names for clarity

- Remove persisted auto-update dir so upstream 127.0.0.1 binary is not used

- Run bridge from /usr/bin via new BRIDGE_BIN variable

- Kill both bridge and proton-bridge process names on init

Prevents Proton auto-updates from reverting IMAP/SMTP to loopback-only.
This commit is contained in:
GitHub Actions
2026-07-01 16:38:10 +02:00
parent d223629418
commit 8bf274ff69
2 changed files with 19 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Dockerfile
+7 -4
View File
@@ -35,9 +35,12 @@ COPY gpgparams entrypoint.sh /protonmail/
COPY scripts/generate_new_certs.sh /root/generate_new_certs.sh
WORKDIR /protonmail/
# Copy protonmail
COPY --from=build /build/proton-bridge/bridge /usr/bin/
COPY --from=build /build/proton-bridge/proton-bridge /usr/bin/
COPY --from=build /build/proton-bridge/vault-editor /usr/bin/
# Copy Proton Mail Bridge.
# Important: use the patched nogui `bridge` binary as both executable names.
# The upstream `proton-bridge` launcher can auto-update into an official binary
# that still binds IMAP/SMTP to 127.0.0.1, bypassing our 0.0.0.0 patch.
COPY --from=build /build/proton-bridge/bridge /usr/bin/bridge
COPY --from=build /build/proton-bridge/bridge /usr/bin/proton-bridge
COPY --from=build /build/proton-bridge/vault-editor /usr/bin/vault-editor
ENTRYPOINT ["bash", "/protonmail/entrypoint.sh"]