Skip to content

fix: add libfido2-1 and libsecret-1-0 to runtime deps#150

Open
smaier wants to merge 3 commits intoshenxn:masterfrom
smaier:fix/libfido2-deps
Open

fix: add libfido2-1 and libsecret-1-0 to runtime deps#150
smaier wants to merge 3 commits intoshenxn:masterfrom
smaier:fix/libfido2-deps

Conversation

@smaier
Copy link
Copy Markdown

@smaier smaier commented Apr 17, 2026

Problem

Since Proton Bridge 3.22, libfido2-1 is a required runtime dependency that is no longer bundled with the upstream binary. Containers based on this image crash at startup with a missing shared library error (libfido2.so.1).

Fix

Add libfido2-1 to the apt-get install line in the runtime stage of both build/Dockerfile and deb/Dockerfile. libsecret-1-0 and ca-certificates were already present. --no-install-recommends and rm -rf /var/lib/apt/lists/* are preserved.

References

Refs #135, #141, #147

Tested

Built and pushed a patched image for linux/amd64 under my Docker Hub namespace (smaier/protonmail-bridge) for verification.

smaier added 3 commits April 17, 2026 12:48
Since Proton Bridge 3.22, libfido2-1 is a required runtime dependency that
was missing from the Docker image, causing container crashes on startup with
a missing library error. libsecret-1-0 and ca-certificates were already
present; only libfido2-1 is added here.

Refs shenxn#135, shenxn#141, shenxn#147
Proton Bridge 3.22+ links against libfido2 via CGo. The build stage
needs libfido2-dev (headers + pkg-config) in addition to the runtime
libfido2-1 already added.
libfido2 requires libcbor at link time via CGo; libcbor-dev was
missing from the build stage, causing ld to fail.
@smaier smaier marked this pull request as ready for review April 17, 2026 11:46
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

Successfully merging this pull request may close these issues.

1 participant