SoftEtherVPN / SoftEtherVPN/SoftetherVPN-docker
Error loading shared library libcpu_features.so
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 111
- Forks
- 31
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
➜ SoftetherVPN-docker git:(master) ✗ docker logs --follow softethervpn-docker-softether-1
Error loading shared library libcpu_features.so: No such file or directory (needed by /usr/local/lib/libmayaqua.so)
Error relocating /usr/local/lib/libmayaqua.so: GetX86Info: symbol not found
Error loading shared library libcpu_features.so: No such file or directory (needed by /usr/local/lib/libmayaqua.so)
Error relocating /usr/local/lib/libmayaqua.so: GetX86Info: symbol not found
Error loading shared library libcpu_features.so: No such file or directory (needed by /usr/local/lib/libmayaqua.so)
Error relocating /usr/local/lib/libmayaqua.so: GetX86Info: symbol not found
Error loading shared library libcpu_features.so: No such file or directory (needed by /usr/local/lib/libmayaqua.so)
Error relocating /usr/local/lib/libmayaqua.so: GetX86Info: symbol not found
Error loading shared library libcpu_features.so: No such file or directory (needed by /usr/local/lib/libmayaqua.so)
Error relocating /usr/local/lib/libmayaqua.so: GetX86Info: symbol not found
Error loading shared library libcpu_features.so: No such file or directory (needed by /usr/local/lib/libmayaqua.so)
Error relocating /usr/local/lib/libmayaqua.so: GetX86Info: symbol not found
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure from the Docker logs and inspect the repository's Dockerfile and image startup configuration. Trace why /usr/local/lib/libmayaqua.so cannot find libcpu_features.so or GetX86Info, then verify that the container starts without the reported loader and relocation errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100