AppImage: Difference between revisions
(Created page with "AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl.") |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl. | [https://appimage.org AppImages] allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses [[musl]]. | ||
== Installation == | |||
First you need FUSE for AppImages to work and modprobe it. | |||
<pre> | |||
# apk add fuse | |||
# modprobe fuse | |||
</pre> | |||
Optional but recommended install [https://git.adelielinux.org/adelie/gcompat gcompat] for glibc compatibility. | |||
<pre> | |||
# apk add gcompat | |||
</pre> | |||
== Usage == | |||
You have to make the AppImage executable, so you can execute it. | |||
=== Example === | |||
<pre> | |||
$ chmod +x Example.AppImage | |||
$ ./Example.AppImage | |||
</pre> | |||
Latest revision as of 19:24, 11 November 2025
AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl.
Installation
First you need FUSE for AppImages to work and modprobe it.
# apk add fuse # modprobe fuse
Optional but recommended install gcompat for glibc compatibility.
# apk add gcompat
Usage
You have to make the AppImage executable, so you can execute it.
Example
$ chmod +x Example.AppImage $ ./Example.AppImage