Skip to content

Missing libfido2 dependency on 3.22 #135

Open

Description

@koolershaker

Hello,

My container won’t start since upgrading to 3.22 due to a missing libfido2 dependency.

I modified the Dockerfile to make it work again by adding libfido2-dev and libcbor-dev.

The build image could be golang, but it currently does not support riscv64. Only debian:sid does, at the time of writing.

FROM debian:sid-slim AS build

ARG version

Install dependencies

RUN apt-get update && apt-get install -y golang build-essential libsecret-1-dev libfido2-dev libcbor-dev

Build

ADD https://github.com/ProtonMail/proton-bridge.git#${version} /build/
WORKDIR /build/
RUN make build-nogui vault-editor

FROM debian:sid-slim
LABEL maintainer="Simon Felding sife@adm.ku.dk"

EXPOSE 25/tcp
EXPOSE 143/tcp

Install dependencies and protonmail bridge

RUN apt-get update
&& apt-get install -y --no-install-recommends socat pass libsecret-1-0 libfido2-1 libcbor-dev ca-certificates
&& rm -rf /var/lib/apt/lists/*

Copy bash scripts

COPY gpgparams entrypoint.sh /protonmail/

Copy protonmail

COPY --from=build /build/bridge /protonmail/
COPY --from=build /build/proton-bridge /protonmail/
COPY --from=build /build/vault-editor /protonmail/

ENTRYPOINT ["bash", "/protonmail/entrypoint.sh"]

Activity

  1. Caleb9 commented on Feb 11, 2026

    @Caleb9

    Same here. I proposed a fix PR.

  2. FaySmash commented on Feb 16, 2026

    @FaySmash

    Not pretty, but I found it easier to add this to my existing docker compose:

        entrypoint: /bin/bash
        command: -c "apt-get update && apt-get install -y libfido2-dev libcbor-dev libfido2-1 && bash /protonmail/entrypoint.sh"
    

    it kinda seems like this repo got abandoned, I hope some new maintainer will pick it up again.

  3. thiswillbeyourgithub commented on Feb 17, 2026

    @thiswillbeyourgithub

    Thanks a lot @Caleb9 it worked for me

  4. Cleyton1 commented on Feb 18, 2026

    @Cleyton1

    Having the same issue here regarding the library being missing. Tried to install 3.19.0-build through docker run, but it gets updated automatically to 3.22, which is missing the library. I then tried to install 3.19 using docker compose, but then I get an error about an orphan container, and another container gets created. I also tried Fay's approach but then getting a "/bin/bash: init: No such file or directory" error. It does look like this project was abandoned :-(

  5. thiswillbeyourgithub commented on Feb 18, 2026

    @thiswillbeyourgithub

    I do think you're not using docker correctly @Cleyton1 . I suggest you try to get it sorted with LLMs.

  6. thiswillbeyourgithub commented on Feb 18, 2026

    @thiswillbeyourgithub

    It looks like fido support was added in 3.22.0 : https://github.com/ProtonMail/proton-bridge/releases

    Currently it looks like I'm getting a lot of timeouts:

    WARN[Feb 18 07:04:11.407] Get "https://proton.me/download/bridge/linux/x86/v1/version.json": dial tcp 185.70.42.45:443: i/o timeout, Attempt 1 pkg=gpa/client

    Same with quite a few other endpoints, until attempts ran out.

    Anyone has a fix?

  7. thiswillbeyourgithub commented on Feb 18, 2026

    @thiswillbeyourgithub

    Nevermind it looks it was a VPN route misconfig that was blocking internet from the container :)

  8. Cleyton1 commented on Feb 18, 2026

    @Cleyton1

    I do think you're not using docker correctly @Cleyton1 . I suggest you try to get it sorted with LLMs.

    I am not going to rule out there maybe a mistake on my end, but I am not having any Docker issue with anything else in my Homelab, either by using docker compose or docker run.

  9. sdtheisen commented on Feb 19, 2026

    @sdtheisen

    Someone please review this PR. @shenxn hope all is well with you...

  10. added a commit that references this issue on Feb 24, 2026
    798e66e
  11. matt-rgx commented on Feb 24, 2026

    @matt-rgx

    Hi, same issue here with the 3.22 auto-update. Is there an ETA for the PR #139 to be merged and a new image to be published? In the meantime I've blocked auto-updates by mounting a read-only empty directory on the updates folder. Thanks!

  12. added a commit that references this issue on Feb 25, 2026
    5ad6fa8
  13. dancwilliams commented on Feb 25, 2026

    @dancwilliams

    For my own sanity I moved forward with forking and producing my own images to handle these issues. Feel free to test out the new images I produced. Here is the repo with docs: https://github.com/dancwilliams/protonmail-bridge-docker

  14. Jycreyn commented on Feb 26, 2026

    @Jycreyn

    For my own sanity I moved forward with forking and producing my own images to handle these issues. Feel free to test out the new images I produced. Here is the repo with docs: https://github.com/dancwilliams/protonmail-bridge-docker

    Seems to work for me, i′m able to send emails. But i got errors.

    Where to open issue ?

    Thanks for your job

  15. dancwilliams commented on Feb 26, 2026

    @dancwilliams

    For my own sanity I moved forward with forking and producing my own images to handle these issues. Feel free to test out the new images I produced. Here is the repo with docs: https://github.com/dancwilliams/protonmail-bridge-docker

    Seems to work for me, i′m able to send emails. But i got errors.

    Where to open issue ?

    Thanks for your job

    Glad it is working. Here is the link for issues. Had to back Lee then since it is a fork. Good catch.

    https://github.com/dancwilliams/protonmail-bridge-docker/issues

  16. Cleyton1 commented on Feb 26, 2026

    @Cleyton1

    For my own sanity I moved forward with forking and producing my own images to handle these issues. Feel free to test out the new images I produced. Here is the repo with docs: https://github.com/dancwilliams/protonmail-bridge-docker

    Seems to work for me, i′m able to send emails. But i got errors.
    Where to open issue ?
    Thanks for your job

    Glad it is working. Here is the link for issues. Had to back Lee then since it is a fork. Good catch.

    https://github.com/dancwilliams/protonmail-bridge-docker/issues

    Well great Sir, thank you a lot for taking the initiative to continue this work, and making it accessible to all of us. Will definitely check it out. Much appreciated. o7

  17. dancwilliams commented on Feb 26, 2026

    @dancwilliams

    @Cleyton1 thanks for the feedback. This is something I use every day, and I figured, what the heck, it's time to give back a little bit, I suppose. I'm setting up some workflows to make sure not only that it updates whenever ProtonMail updates, but also whenever the underlying containers have updates and packages and things like that, to kind of help not only keep ProtonMail up to date and test for some of the issues we ran into with the latest release, but also keep up to date on the security of the underlying container.

  18. patricksthannon commented on Feb 27, 2026

    @patricksthannon

    I didn't realize even the self hosted bridge could only be used with a paid subscription... :/ . But anyways, here's the fix using @FaySmash dependency add and leveraging a Docker Compose pulling a Dockerfile in the same directory.

    Dockerfile

    FROM shenxn/protonmail-bridge
    
    USER root
    RUN apt-get update && \
        apt-get install -y libfido2-1 libfido2-dev libcbor-dev && \
        rm -rf /var/lib/apt/lists/*
    

    Docker Compose.yaml

    version: '2.1'
    services:
      protonmail-bridge:
        build: .
        container_name: protonmail-bridge
        ports:
          - 1025:25/tcp
          - 1143:143/tcp
        restart: unless-stopped
        volumes:
          - protonmail:/root
    volumes:
      protonmail:
        name: protonmail
    
  19. matt-rgx commented on Feb 27, 2026

    @matt-rgx

    Thank you a lot for the fork @dancwilliams ! Keep up the good work

  20. NoelleAttachedStorage commented on Mar 1, 2026

    @NoelleAttachedStorage

    @dancwilliams you're a legend. I relied on this container for my unraid syslog notifications and nextcloud account registrations/password changes.

  21. jfgsilva commented on Mar 2, 2026

    @jfgsilva

    For my own sanity I moved forward with forking and producing my own images to handle these issues. Feel free to test out the new images I produced. Here is the repo with docs: https://github.com/dancwilliams/protonmail-bridge-docker

    Hey @dancwilliams thx for this. I used your image as drop in replacement for my pod. works flawlessly. Let me know if you need help

  22. added a commit that references this issue on Apr 11, 2026
    c44c826
  23. PaulKierstead commented on Apr 21, 2026

    @PaulKierstead

    For my own sanity I moved forward with forking and producing my own images to handle these issues. Feel free to test out the new images I produced. Here is the repo with docs: https://github.com/dancwilliams/protonmail-bridge-docker

    Dammit that is nice work I only discover after i go fix up the docker file myself lol. Yours is much nicer! I shall adopt it I think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions