You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :-(
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.
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!
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
Reacted by User-U812, Joost, João Filipe Silva, Bergbok, Ben Hovinga and David Mungin
Reacted by rettoph, Jycreyn, Manuel Thalmann, NoelleAttachedStorage, Bergbok, Ben Hovinga, freakshock88, JoLo and David Mungin
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.
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.
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.
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
@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.
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/*
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
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
Activity
Caleb9 commentedon Feb 11, 2026
Same here. I proposed a fix PR.
FaySmash commentedon Feb 16, 2026
Not pretty, but I found it easier to add this to my existing docker compose:
it kinda seems like this repo got abandoned, I hope some new maintainer will pick it up again.
thiswillbeyourgithub commentedon Feb 17, 2026
Thanks a lot @Caleb9 it worked for me
Cleyton1 commentedon Feb 18, 2026
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 :-(
thiswillbeyourgithub commentedon Feb 18, 2026
I do think you're not using docker correctly @Cleyton1 . I suggest you try to get it sorted with LLMs.
thiswillbeyourgithub commentedon Feb 18, 2026
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/clientSame with quite a few other endpoints, until attempts ran out.
Anyone has a fix?
thiswillbeyourgithub commentedon Feb 18, 2026
Nevermind it looks it was a VPN route misconfig that was blocking internet from the container :)
Cleyton1 commentedon Feb 18, 2026
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.
sdtheisen commentedon Feb 19, 2026
Someone please review this PR. @shenxn hope all is well with you...
Add libfido2 dependency for Bridge v3.22.0
matt-rgx commentedon Feb 24, 2026
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!
Fix v3.22.0 build, improve stability, and set up for community mainte…
dancwilliams commentedon Feb 25, 2026
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
Jycreyn commentedon Feb 26, 2026
Seems to work for me, i′m able to send emails. But i got errors.
Where to open issue ?
Thanks for your job
dancwilliams commentedon Feb 26, 2026
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
Cleyton1 commentedon Feb 26, 2026
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
dancwilliams commentedon Feb 26, 2026
@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.
patricksthannon commentedon Feb 27, 2026
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
Docker Compose.yaml
matt-rgx commentedon Feb 27, 2026
Thank you a lot for the fork @dancwilliams ! Keep up the good work
NoelleAttachedStorage commentedon Mar 1, 2026
@dancwilliams you're a legend. I relied on this container for my unraid syslog notifications and nextcloud account registrations/password changes.
jfgsilva commentedon Mar 2, 2026
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
Add libfido2 dependency for Bridge v3.22.0
fix: add libfido2-1 and libsecret-1-0 to runtime deps
PaulKierstead commentedon Apr 21, 2026
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
fix: add libfido2-1 and libsecret-1-0 to runtime deps
fix(docker): add missing library
fix(docker): add missing libfido2-1 library