[GH-ISSUE #6313] [Bug] The libalpm version is affecting the error. #2791

New issue

Open

opened 2026-03-23 21:25:11 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 21:25:11 +00:00

Owner

Originally created by @yottan0304 on GitHub (Sep 15, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6313

Bug Description

Docker Build Failure: A Docker build process is failing due to a version mismatch of the libalpm.so library.
Version Conflict: The yay package, which relies on libalpm.so, was built against an older version (14) but is now trying to use a newer version (15).
Potential Solutions:
Modify Dockerfile: Directly adjust the Dockerfile to address the version incompatibility.
Waiting for an update to archlinux/archlinux is another possible solution.

The fix is to add the following to # Install yay in the Dockerfile:
RUN sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14

Error Log:

 => ERROR [app builder  9/27] RUN curl -sSfL     --output yay.tar.gz     https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_x86_64.tar.gz &&   tar -xf yay.tar.gz &&   sudo mv yay_12.3.3_x86_  1.3s
------                                                                                                                                                                                                              
 > [app builder  9/27] RUN curl -sSfL     --output yay.tar.gz     https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_x86_64.tar.gz &&   tar -xf yay.tar.gz &&   sudo mv yay_12.3.3_x86_64/yay /bin &&   rm -rf yay_12.3.3_x86_64 &&   yay --version:                                                                                                                                                                     
1.214 yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory                                                                                           
------                                                                                                                                                                                                              
failed to solve: process "/bin/sh -c curl -sSfL     --output yay.tar.gz     https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_x86_64.tar.gz &&   tar -xf yay.tar.gz &&   sudo mv yay_12.3.3_x86_64/yay /bin &&   rm -rf yay_12.3.3_x86_64 &&   yay --version" did not complete successfully: exit code: 127

How to Reproduce

When I built it following the steps in Docker

Expected Behavior

See Bug Description

Operating System

Ubuntu 22.04.3 LTS(WSL)

AppFlowy Version(s)

0.69

Screenshots

No response

Additional Context

No response

Originally created by @yottan0304 on GitHub (Sep 15, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6313 ### Bug Description Docker Build Failure: A Docker build process is failing due to a version mismatch of the libalpm.so library. Version Conflict: The yay package, which relies on libalpm.so, was built against an older version (14) but is now trying to use a newer version (15). Potential Solutions: Modify Dockerfile: Directly adjust the Dockerfile to address the version incompatibility. Waiting for an update to archlinux/archlinux is another possible solution. The fix is to add the following to # Install yay in the Dockerfile: `RUN sudo ln -s /usr/lib/libalpm.so.15.0.0 /usr/lib/libalpm.so.14` Error Log: ``` => ERROR [app builder 9/27] RUN curl -sSfL --output yay.tar.gz https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_x86_64.tar.gz && tar -xf yay.tar.gz && sudo mv yay_12.3.3_x86_ 1.3s ------ > [app builder 9/27] RUN curl -sSfL --output yay.tar.gz https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_x86_64.tar.gz && tar -xf yay.tar.gz && sudo mv yay_12.3.3_x86_64/yay /bin && rm -rf yay_12.3.3_x86_64 && yay --version: 1.214 yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory ------ failed to solve: process "/bin/sh -c curl -sSfL --output yay.tar.gz https://github.com/Jguer/yay/releases/download/v12.3.3/yay_12.3.3_x86_64.tar.gz && tar -xf yay.tar.gz && sudo mv yay_12.3.3_x86_64/yay /bin && rm -rf yay_12.3.3_x86_64 && yay --version" did not complete successfully: exit code: 127 ``` ### How to Reproduce When I built it following the steps in [Docker](https://docs.appflowy.io/docs/appflowy/install-appflowy/installation-methods/installing-with-docker) ### Expected Behavior See Bug Description ### Operating System Ubuntu 22.04.3 LTS(WSL) ### AppFlowy Version(s) 0.69 ### Screenshots _No response_ ### Additional Context _No response_

mirror added the

desktop

bug

labels

2026-03-23 21:25:11 +00:00

mirror commented

2026-03-23 21:25:11 +00:00

Author

Owner

@rileyhawk1417 commented on GitHub (Sep 25, 2024):

Seems like Paru also has the same issue the simplest thing might be to upgrade to the git version for now.

In the paru repo someone came up with a replacement PKGBUILD and on yay they suggested removing & reinstalling it. Although I think you would also need the git version of yay.

@rileyhawk1417 commented on GitHub (Sep 25, 2024): Seems like Paru also has the same issue the simplest thing might be to upgrade to the git version for now. In the paru repo someone came up with a replacement [PKGBUILD](https://github.com/Morganamilo/paru/issues/1239#issuecomment-2351465944) and on yay they suggested [removing & reinstalling it](https://github.com/Jguer/yay/issues/2508#issuecomment-2360021446). Although I think you would also need the git version of yay.

mirror referenced this issue

2026-03-23 22:18:41 +00:00

[PR #2791] [MERGED] chore: some ui improvements #5423