AppFlowy-IO / AppFlowy-IO/AppFlowy
[Bug] The libalpm version is affecting the error.
- Vorherrschende Sprache
- Dart
- Sterne
- 76.6k
- Forks
- 6k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### 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_
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.