Error after upgrade form V2 to V3: version 'GLIBC_2.28' not found
Heziode opened this issue · 16 comments
After upgrading from 2.3.0-1 to 3.0.17-1 I got the following error:
/usr/lib/protonmail/bridge/bridge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/protonmail/bridge/bridge)
FATA[Feb 23 10:23:06.923] Failed to launch error="exit status 1" exe_path=/usr/lib/protonmail/bridge/bridge exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.0.17
I can confirm this, receiving the same message
edit: will probably have to bump Ubuntu from bionic to either focal or jammy
if you execute ldd —version inside the container it shows version 2.27
I'm getting the same error too
also, from what i heard this morning, with all the new changes in the main branch
https://github.com/shenxn/protonmail-bridge-docker/blob/master/build/build.sh#L8 - this will no longer build unless this repo uses the proper libraries and etc.
ProtonMail/proton-bridge#323 see here for resolution.
EDIT: the fixes work, however, since it's using an unstable branch it is not recommended. updates to v3.X.X should be disabled until they work. For those curious, this works: https://github.com/larivierec/protonmail-bridge-docker/blob/master/build/VERSION and i've tried it with docker run
After upgrading from
2.3.0-1to3.0.17-1I got the following error:/usr/lib/protonmail/bridge/bridge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/protonmail/bridge/bridge) FATA[Feb 23 10:23:06.923] Failed to launch error="exit status 1" exe_path=/usr/lib/protonmail/bridge/bridge exe_to_launch=bridge launcher_path=/usr/lib/protonmail/bridge/proton-bridge launcher_version=3.0.17
I'm getting the same error
Same issue here on Synology DS218+ on dsm version 7.1.1-42962 Update 4.
Good afternoon,
I've been using this container for a long time but it suddenly stopped working. I can now confirm the issue is happening due to the new version of GLIBC. Moreover, going back to a previous version seems not to work because of the shared directories inside the container (I think .cache is the culprit).
I'll try to look for a solution and share it on this thread if there's any. If possible, it would be interesting to have the container updated to the latest version of the distribution protonmail that is being shipped with.
I can confirm the .cache is the culprit - I had it bind-mounted inside the container (I did it for the hole container's /root directory).
Deleting the .cache directory and simply bind mounting the required directories (AFAIK, .config, .local, .gnupg and .password-store) does the trick. Then, going back to v2.* works again fine - no re-configuration needed.
Same issue here on Synology DS218+ on dsm version 7.1.1-42962 Update 4.
Same here on a DS720+
same with unraid :(
This project still seems to be pushing updates to the docker hub location even though they don't work because of this error. Automation is truly a blessing and a curse.
I rolled back my docker tag to "2.4.8-1" and that still works.
how did you do that in unraid?
how did you do that in unraid?
I don't use unraid so I'm not sure.
I just wanted to let the community know that rolling back to that version of the docker image worked. I did have to clear the .cache directory first as @Javinator9889 pointed out. I'm sure @larivierec change and pull request will work too once it is accepted into this project. There's been no activity from @shenxn in a while -- I'm hoping this project is not abandoned.
how did you do that in unraid?
You specify the tag in repository field
e.g. instead of shenxn/protonmail-bridge
add the tag of the verison you want to use like below
shenxn/protonmail-bridge:2.3.0-1
Be aware that if you specify the tag it will never say an update is available, since you've pinned the version.
I can confirm that this issue is now fixed after commit #80. However, I had to reinstall my container, maybe clearing some files would've been enough.
Yes its working just like before after the update