add environment variable to force specific libc and disable all probing methods
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 78
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
We build AppImages that work on Any linux system. In order to do this we need to bundle our own dynamic linker + glibc.
We have had several issues with Electron apps crashing on alpine linux, because they think the system is musl due to the app running /usr/bin/ldd.
- https://github.com/pkgforge-dev/Tutanota-Desktop-AppImage-Enhanced/commit/135beaee14e6b0dbff5cabe220fd560c18ac1cc6
- https://github.com/pkgforge-dev/UnityHub-AppImage/commit/4c830c5d5210644fda9a39d3c2d2fcf0b8edced0
This works fine for most applications, however there are apps that do integrity checks of their app.asar and in that case we are very screwed: https://github.com/pkgforge-dev/Anylinux-AppImages/issues/786#issuecomment-5378649595
Can you add something like DETECT_LIBC_FORCE=glibc?
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
No file or test is named in the issue. Start by locating the module's libc detection entry point and existing tests, then trace how environment information is probed; done means an environment variable can force the requested libc and prevent other probing methods, with tests covering the override.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100